Uh oh!
There was an error while loading. Please reload this page.
Move API SHA bump to its own script - #5151
Merged
Merged
Conversation
We are now updating the API docs SHA much more frequently than monthly, so let's decouple it from the monthly Craft version bump.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
chadwhitacre
enabled auto-merge (squash)
June 16, 2022 15:01
chadwhitacre added a commit
to getsentry/develop
that referenced
this pull request
Jun 16, 2022
chadwhitacre
commented
Jun 16, 2022
ContributorAuthor
Oh geez automerge in repo w/ no branch protection. 🤦♂️ |
ContributorAuthor
Ftr here's where the API SHA bump was added to |
This file contains hidden or 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
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Overloading the
bump-version.shCraft hook to also be used from localhost during more-frequent API doc updates added some inter-environment friction that resulted in a CalVer release failure.Seems great to update the API docs more frequently than once a month, and that means it would be redundant to also do this during monthly CalVer release, so let's move that to a separate script.