bump-workspaces
A tool for upgrading Deno workspace packages using conventional commits
by denolandTypeScript
Commit activity
Last 12 weeks · 0 commits
Community health
2 of 6 standards met
50
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template
Recent PRs & issues
Quiet · 7 discussions · Last activity 7mo ago
See all on GitHub →
FEATURE-REQUEST: Aliases for package scopes to reduce the number of words in the commit titleOpenIssue
https://github.com/jsr-probitas/probitas-client I'm trying this bump-workspaces with the above project but I couldn't get it work unless I use or so on. I've tried. (THIS ONE WORK)
Scenario I have two packages in the workspace: and . depends on (i.e. depends on ). Then, I make a breaking change in and run this CLI. Actual result It makes a minor release of . That's fine. Expected result It should also make a minor release of , which would be dependent on . Otherwise there is still that relies on , which isn't compatible with . Therefore, there is no chance to get of version that depends on , though technically it exists and must be published. This would be consistent e.g. with - How dependencies are bumped: For example, if I have two packages: at and at that depends on at . If I add to a changeset with a change, the version of within the mono-repo should also be updated. If it is not, either in the mono-repo will not use in development, or in development will not match an installation of in production. As such we end up with a changeset that includes as and as . All updating of dependencies is done as a patch bump. If you want to indicate a more significant change to from consuming a new version of , we recommend adding a second changeset specifically for .
Is there any plan to enable this so it could be use on projects with no workspaces but just a deno.json with specified version at the root? something like this:
Recent fixes
Example [!NOTE] See issue
As is common with conventional commits, breaking changes are often denoted with a rather than the commit type. Supporting this syntax will allow more flexibility for users of the package. It will also allow breaking changes to occur in multiple different types of commits, which is a more realistic scenario in the real world. I prefaced the title with because I just begun implementing this. I'll open a PR for it later today or tomorrow. Thanks!
Structured data for AI agents
Repository: denoland/bump-workspaces. Description: A tool for upgrading Deno workspace packages using conventional commits Stars: 17, Forks: 6. Primary language: TypeScript. Languages: TypeScript (100%). License: MIT. Homepage: https://jsr.io/@deno/bump-workspaces Topics: conventional-commits, deno, monorepo, workspaces. Latest release: 0.1.23 (7mo ago). Open PRs: 0, open issues: 7. Last activity: 7mo ago. Community health: 50%. Top contributors: kt3k, eser, dkolba, denobot, elcoosp.