ci: re-pin dev-kit reusable workflow to released v1.0.14 - #751
Merged
Conversation
Contributor
|
Important Review available on request
Reviews should be triggered manually for repositories with fewer than 10 stars. Select Trigger review above or comment ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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 free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What
# post-v1.0.13note to# v1.0.14(same SHA, dev-kit tagged it -> feat: add reusable renovate-auto-approve workflow dev-kit#25)Why
Renovate cant parse the freeform comment, so every run logs a package lookup failure for the dev-kit pin on the dependency dashboard (#133). With the release tagged and the standard
# vX.Y.Zformat, the pin becomes a normal tracked update.Testing
Comment-only change,
uses:SHA is identical to whats deployed. The dashboard warning should disappear on the next Renovate run after merge.Checklist