Support .changesets #24882
Replies: 10 comments
-
Hi there, Get your issue fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. To get started, please read our guide on creating a minimal reproduction. We may close the issue if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
-
Requires team design, can't supply more minimal reproduction. |
Beta Was this translation helpful? Give feedback.
-
Can you make a simple repository with just one dependency which uses changesets for its changelog? That way we can see what Renovate does today, and we can use that repository to test the new feature. |
Beta Was this translation helpful? Give feedback.
-
I am also in need of this feature. Here is a simple repository with one (non-dev) dependency which uses changesets for its changelog https://github.com/jonathanmorley/renovate-changeset-repro. To be compatible with changeset, I would expect https://github.com/jonathanmorley/renovate-changeset-repro/pull/3 to include changeset(s) that describes the changes being made per workspace package being updated (this is a single package repo, but changesets supports monorepos) See https://github.com/jonathanmorley/renovate-changeset-repro/commit/1b6cbdb387572e7ef24d0e75c3e985ab80bff78f for an example changeset, and https://github.com/jonathanmorley/renovate-changeset-repro/blob/main/CHANGELOG.md for how that was absorbed into the changelog (and influences the type of version bump performed). |
Beta Was this translation helpful? Give feedback.
-
Hello, I am also trying to work around this on my repository. I've been trying to use the postUpgradeTask to add the files by myself for now but it's not working great (Files are ignored). I'd be willing to give it a go if you can give me some pointer on where to start |
Beta Was this translation helpful? Give feedback.
-
Related changeset issue for automating this from the other direction: changesets/changesets#647 |
Beta Was this translation helpful? Give feedback.
-
Would love to see this added. I've seen this GH Action across a few repos, but can't seem to get it working in the repo I'm currently working in. https://github.com/the-guild-org/shared-config/blob/main/.github/workflows/changesets-dependencies.yaml |
Beta Was this translation helpful? Give feedback.
-
While I haven't tried the approach above (or the one linked in changesets/changesets#647, https://github.com/backstage/backstage/blob/master/.github/workflows/sync_renovate-changesets.yml), I have tried to push commits to a renovate PR before (which appear to be what these are doing), and have seen renovate then refuse to update the PR any further. I would like to avoid that behaviour |
Beta Was this translation helpful? Give feedback.
-
You can use |
Beta Was this translation helpful? Give feedback.
-
I've spun up a Github Action to help deal with this: https://github.com/mscharley/dependency-changesets-action Still very early days, but I've been using it on one repo without issues. There's probably no reason it wouldn't work with other services like dependabot as well, but I haven't done any testing with that yet. |
Beta Was this translation helpful? Give feedback.
-
What would you like Renovate to be able to do?
Renoatev can today use conventional commits when it's submitting a NEW PR
However some monorepos choose to to manage their changelog using https://github.com/changesets/changesets.
Changesets is a popular solution for note based version managenet tracking and automation and is the recommended approach by several mono repo build tools (1).
I sugget that renovate idenitfy if the repository is a changesets managed monorepo, and if it the case generate changeset notes as part of the Pull Request.
If you have any ideas on how this should be implemented, please tell us here.
Take the PR content generator and generalize it's output by implementation.
Is this a feature you are interested in implementing yourself?
No
Beta Was this translation helpful? Give feedback.
All reactions