-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release/2022.10.1 #1527
Merged
Merged
Release/2022.10.1 #1527
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* Run CI on branchs release/** * Update pyproject.toml to use calver * Update on branch
* update welcome messge * remove qhub specifics from theme
* Name change: .github * Name change: qhub/ * Name change: tests/ * Name change: tests_deployment/ * Name change: tests_e2e/ * Name change: / * Rename folder * Rename releases * Remove qhub/ * Run pre-commit * Revert docs links * Fix infracost artifact names * Update upgrade command + test * Updates based on review * Update step output format * Fix: Update step output format * Update nebari/provider/cicd/common.py Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update stage 08 folder names * Update nebari/schema.py Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/02-infrastructure/azure/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/02-infrastructure/do/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/02-infrastructure/gcp/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/02-infrastructure/gcp/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/03-kubernetes-initialize/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/05-kubernetes-keycloak/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/06-kubernetes-keycloak-configuration/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/06-kubernetes-keycloak-configuration/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/template/stages/07-kubernetes-services/modules/kubernetes/forwardauth/variables.tf Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update setup.cfg Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update scripts/aws-force-destroy.py Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update setup.cfg Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update setup.cfg Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update setup.cfg Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update setup.cfg Co-authored-by: Tania Allard <taniar.allard@gmail.com> * Update nebari/constants.py Co-authored-by: Vinicius D. Cerutti <51954708+viniciusdc@users.noreply.github.com> * Update setup.cfg Co-authored-by: Tania Allard <taniar.allard@gmail.com> * fix flake8 complaint * Update ref to qhub-dask to nebari-dask * Update readme * Change to PYPI_API_TOKEN Co-authored-by: viniciusdc <vinivdc2009@hotmail.com> Co-authored-by: Tania Allard <taniar.allard@gmail.com> Co-authored-by: Vinicius D. Cerutti <51954708+viniciusdc@users.noreply.github.com>
…#1509) * qhub/initialize: lazy load attributes that require remote information * Fix broken configuration * fix renaming * fix header text * Update nebari/initialize.py * Update nebari/initialize.py * Blackify Co-authored-by: Amit Kumar <dtu.amit@gmail.com> Co-authored-by: Nebari-sensei <116370392+nebari-sensei@users.noreply.github.com>
* Add fix, enhancements and pytests for CLI * No zero-padded month for CalVer release branches * Update cli test * Simplify test.yaml
* Remove old cli * Update theme * Remove shim * display_version: True
* Add release notes for 2022.10.1 * Wording * Update README.md with new docs links * Update README.md with new docs links Co-authored-by: Vinicius D. Cerutti <51954708+viniciusdc@users.noreply.github.com>
💰 Infracost estimate: monthly cost will not change
9 projects have no cost estimate changes. Infracost output
This comment will be updated when the cost estimate changes. Is this comment useful? Yes, No, Other |
aktech
approved these changes
Nov 1, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎉
* Remove leading v for release tags * Add note to release checklist * Merge release branch into main
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes | Closes | Resolves #1504
Changes introduced in this PR:
2022.10.1
release changes intomain
🎉Types of changes
What types of changes does your PR introduce?
Put an
x
in the boxes that applyTesting
Requires testing
In case you checked yes, did you write tests?
Documentation
Does your contribution include breaking changes or deprecations?
If so have you updated the documentation?
Further comments (optional)
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered and more.