2023.1.1rc1

Release candidate 1 for 2023.11.1.

2022.11.1

What's Changed

• cherry-pick Update README logo (#1514) by @aktech in #1517
• Release/2022.10.1 by @iameskild in #1527
• Add Note about QHub->Nebari rename in old docs by @pavithraes in #1543
• 🔄 Synced file(s) with nebari-dev/.github by @nebari-sensei in #1550
• 🔄 Synced file(s) with nebari-dev/.github by @nebari-sensei in #1551
• 🔄 Synced file(s) with nebari-dev/.github by @nebari-sensei in #1555
• 🔄 Synced file(s) with nebari-dev/.github by @nebari-sensei in #1560
• Small CLI fixes by @iameskild in #1529
• 🔄 Synced file(s) with nebari-dev/.github by @nebari-sensei in #1561
• Render github actions configurations as yaml by @aktech in #1528
• Update "QHub" to "Nebari" in example notebooks by @pavithraes in #1556
• Update links to Nebari docs in guided init by @pavithraes in #1557
• CI: Spinup unique cirun runners for each job by @aktech in #1563
• Issue-1417: Improve Dask workers placement on AWS | fixing a minor typo by @limacarvalho in #1487
• Update setup-node version by @iameskild in #1570
• Facilitate CI run for contributor PR by @aktech in #1568
• Action to sync release notes with nebari-docs by @pavithraes in #1554
• Restore how the dask worker node group is selected by default by @iameskild in #1577
• Fix skip check for workflows by @aktech in #1578
• 📝 Update readme by @trallard in #1579
• MAINT - Miscellaneous maintenance tasks by @trallard in #1580
• Wait for Test PyPI to upload test release by @iameskild in #1583
• Add release notes for 2022.11.1 by @iameskild in #1584

New Contributors

• @nebari-sensei made their first contribution in #1550
• @limacarvalho made their first contribution in #1487

Full Changelog: v0.4.5...2022.11.1

2022.11.1rc4

Release candidate 4 for 2022.11.1.

2022.11.1rc3

Release candidate 3 for 2022.11.1.

2022.11.1rc2

Release candidate 2 for 2022.11.1.

2022.11.1rc1

Release candidate 1 for 2022.11.1.

2022.10.1 - October 31, 2022

WARNING

The project has recently been renamed from QHub to Nebari. If your deployment is still managed by qhub performing an in-place upgrade will IRREVOCABLY BREAK your deployment. This will cause you to lose any data stored on the platform, including but not limited to NFS (filesystem) data, conda-store environments, Keycloak users and groups, etc. Please backup your data before attempting an upgrade.

Feature changes and enhancements

We are happy to announce the first official release of Nebari (formerly QHub)! This release lays the groundwork for many exciting new features and improvements.

This release introduces several important changes, which include:

• a major project name change from QHub to Nebari - PR 1508
• a switch from the SemVer to CalVer versioning format - PR 1501
• a new, Typer-based CLI for improved user experience - PR 1443 + PR 1519

Although breaking changes are never fun, the Nebari development team believes these changes are important for the immediate and future success of the project. If you experience any issues or have questions about these changes, feel free to open an issue on our Github repo.

What's Changed

• Switch to CalVer by @iameskild in #1501
• Update theme welcome messages to use Nebari by @pavithraes in #1503
• Name change QHub --> Nebari by @iameskild in #1508
• qhub/initialize: lazy load attributes that require remote information by @FFY00 in #1509
• Update README logo reference by @viniciusdc in #1514
• Add fix, enhancements and pytests for CLI by @iameskild in #1498
• Remove old CLI + cleanup by @iameskild in #1519
• Update skip_remote_state_provision default value by @viniciusdc in #1521
• Add release notes for 2022.10.1 by @iameskild in #1523

New Contributors

• @pavithraes made their first contribution in #1503
• @FFY00 made their first contribution in #1509

2022.10.1rc2

Release candidate 2 for 2022.10.1

2022.10.1rc1

Release candidate for 2022.10.1

2022.10.1.dev0 - October 21, 2022

Switch to CalVer.