Automatically bump version to match firebase-tools releases.
#203
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
|
@w9jds This seems to be working! :) Please could you take a look? |
This reverts commit 8daccc5.
w9jds
approved these changes
Dec 8, 2023
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.
This works towards #201.
This initial action runs on a cron schedule (
0 0 * * *- every day). It checks thefirebase-actionandfirebase-toolsversions and does a semver compare. If our version is less than the theirs, it moves onto the second step.The second step replaces the version numbers in the files, and pushes a new tag.
I still need to get the push working, and to get it to trigger a new release.
In the future, it would be better to have this run from a webhook or similar, rather than running on the cron.