US158341 - Use new release token #84
Merged
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
dlockhart
approved these changes
Dec 1, 2023
|
🎉 This PR is included in version 4.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
The
brightspace-botandD2L_GITHUB_TOKENare no longer needed forreleaseworkflows. Instead, we have a newD2L_RELEASE_TOKENthat has the ability to bypass the repo ruleset (configured in https://github.com/Brightspace/repo-settings/pull/1458) and org-level ruleset.Note: This isn't available in the
Brightspaceorg yet, but will be soon!Before merging, I will:
brightspace-botas a repo contributorD2L_RELEASE_TOKENis available and remove this repo's access toD2L_GITHUB_TOKENIf you need to make a cert or hotfix, this will need to be backported to the
20.23.12and20.23.11release branches.