chore: add package repository metadata for Renovate changelogs - #390
Merged
fridajac merged 1 commit intoAug 11, 2026
Merged
Conversation
Point packages at the AxisCommunications monorepo (with directory) via backstage-cli repo fix --publish, and enforce it in CI with yarn fix --check. Should help Renovate show changelog, and users browsing npm finding the repo easily.
|
GabDug
marked this pull request as ready for review
August 8, 2026 11:29
fridajac
approved these changes
Aug 11, 2026
fridajac
left a comment
Contributor
There was a problem hiding this comment.
LGTM! Thanks!! :) No worries about the missing ticket.
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
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.
Hey, I just made a Pull Request!
Context
I noticed Renovate did not include the changelog for the plugins, presumably because of the lack of repository field. While this can be configured manually by end-users, adding the field is a best practice. This should also help users browsing npm packages find the source.
I can't test E2E as it touches packaging/publishing, but the packing step should take care of rewriting entrypoints properly.
Issue ticket number and link
yet again no issue; please let me know if you wish this to stop :D
Checklist before requesting a review