Invalidate bundler cache when cutting a new gem #5930
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
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.
Experimental: trying to work around the problem with the wrong securerandom version being activated when pushing a new gem version.
Note: it is not possible to test the branch fully because my personal fork does not have the necessary AWS permissions to assume roles needed for the standard deployment steps. I've done a simple dry run and confirmed that there are no problems with syntax, and that our "release" github action is able to get my own fork of the drivers-github-tools repository, which has the necessary changes to support invalidating the bundler cache.