v0.4.4rc5 - September 5, 2022

Release Candidate 5 for v0.4.4.

v0.4.4rc4 - September 1, 2022

Release Candidate 4 for v0.4.4.

v0.4.4rc3 - August 18, 2022

Release Candidate 3 for v0.4.4.

v0.4.4rc2 - August 18, 2022

Release Candidate 2 for v0.4.4.

v0.4.4rc1 - August 17, 2022

Release-Candidate 1 for v0.4.4.

v0.4.3 - July 7, 2022

What's Changed

• Update the login/Keycloak docs page by @gabalafou in #1289
• Add configuration option so myst parser generates anchors for heading… by @costrouc in #1299
• Image scanning by @HarshCasper in #1291
• Fix display version behavior by @viniciusdc in #1275
• [Docs] Add docs about custom Identity providers for Authentication by @viniciusdc in #1273
• Add prefect token var to CI when needed by @viniciusdc in #1279
• ci: prevent image scans on main image builds by @HarshCasper in #1300
• Integrate kbatch by @iameskild in #1258
• add retrolab to the base jupyter image by @tonyfast in #1222
• Update pre-commit, remove vale by @iameskild in #1282
• Argo Workflows by @Adam-D-Lewis in #1252
• Update minio, postgresql chart repo location by @iameskild in #1308
• Fix broken AWS, set minimum desired size to 1, enable 0 scaling by @tylerpotts in #1304
• v0.4.2 release notes by @iameskild in #1323
• install dask lab ext from main by @iameskild in #1321
• Overrides default value for dask-labextension by @viniciusdc in #1327
• CI: Add Infracost to GHA CI for infra cost tracking by @HarshCasper in #1316
• Add check for highest supported k8s version by @aktech in #1336
• Increase the default instance sizes by @peytondmurray in #1338
• Add panel-serve as a CDS dashboard option by @iameskild in #1070
• Generate QHub Costs via infracost by @HarshCasper in #1340
• Add release-checklist issue template by @iameskild in #1314
• Fix missing import: rich : broken qhub init with cloud by @aktech in #1353
• Bump qhub-dask version to 0.4.3 by @peytondmurray in #1341
• Remove the need for AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY to be set with Digital Ocean deployment by @costrouc in #1344
• Revert "Remove the need for AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY to be set with Digital Ocean deployment" by @viniciusdc in #1355
• Upgrade kbatch version by @iameskild in #1335
• Drop support for python 3.7 in dask environment by @peytondmurray in #1354
• Add useful terminal utils to jlab image by @dharhas in #1361
• Tweak bashrc by @dharhas in #1363
• Fix bug where vscode extensions are not installing by @viniciusdc in #1360
• Update release notes for 0.4.3 by @iameskild in #1364

New Contributors

• @gabalafou made their first contribution in #1289
• @peytondmurray made their first contribution in #1338
• @dharhas made their first contribution in #1361

Full Changelog: v0.4.1...v0.4.3

v0.4.3rc2 - July 6th, 2022

Release candidate 2 for v0.4.3

v0.4.3rc1 - July 1, 2022

Release-Candidate 1 for v0.4.3.

v0.4.2 - June 9, 2022

Incident postmortem

Bitnami update breaks post v0.4.0 releases

On June 2, 2022, GitHub user @peytondmurray reported issue 1306, stating that he was unable to deploy QHub using either the latest release v0.4.1 or installing qhub from main. As verified by @peytondmurray and others, during your first qhub deploy, the deployment halts and complains about two invalid Helm charts missing from the bitnami index.yaml.

Bitnami's decision to update how long they keep old Helm charts in their index for has essentially broken all post v0.4.0 versions of QHub.

This is a severe bug that will affect any new user who tries to install and deploy QHub with any version less than v0.4.2 and greater than or equal to v0.4.0.

Given the impact and severity of this bug, the team has decided to quickly cut a hotfix.

AWS deployment failing due to old auto-scaler helm chart

On May 27, 2022, GitHub user @tylerpotts reported issue 1302, stating that he was unable to deploy QHub using the latest release v0.4.1 (or installing qhub from main). As described in the original issue, the deployment failed complaining about the deprecated v1beta Kubernetes API. This led to the discovery that we were using an outdated cluster_autoscaler helm chart.

The solution is to update from v1beta to v1 Kubernetes API for the appropriate resources and update the reference to the cluster_autoscaler helm chart.

Given the impact and severity of this bug, the team has decided to quickly cut a hotfix.

Bug fixes

This release is a hotfix for the issue summarized in the following:

• issue 1319
• issue 1306
• issue 1302

v0.4.2rc2 - June 8, 2022

Release Candidate 2 for v0.4.2.