GitShow/denoland/bump-workspaces
denoland

bump-workspaces

A tool for upgrading Deno workspace packages using conventional commits

by denoland
conventional-commitsdenomonorepoworkspaces
Star on GitHubForkWebsitenpm

TypeScript

17 stars6 forks5 contributorsQuiet · 9mo agoSince 20240.1.23MIT

Meet the team

See all 5 on GitHub →
kt3k
kt3k71 contributions
eser
eser3 contributions
dkolba
dkolba1 contribution
denobot
denobot1 contribution
elcoosp
elcoosp1 contribution

Languages

View on GitHub →
TypeScript100%

Commit activity

Last 12 weeks · 0 commits

Full graph →

Community health

2 of 6 standards met

Community profile →
50
✓README✓License○Contributing○Code of Conduct○Issue Template○PR Template

Recent PRs & issues

Quiet · 6 discussions · Last activity 9mo ago
See all on GitHub →
lambdalisue
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)

lambdalisue · 8mo ago
0x009922
Take dependencies into account when bumping versionsOpenIssue

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 .

0x009922 · 1y ago
inverted-capital
truncate PR body to comply with github api limitsOpenIssue

If you make a large number of commits, then the PR body can be generated to exceed 65,536 characters, which will cause the PR to fail.

inverted-capital · 1y ago

Recent fixes

View closed PRs →
danimydev
Enabling version bump for "simpler" reposClosedIssue

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:

danimydev · 1mo ago
elcoosp
feat: exclamation mark post module to signify BREAKINGMergedPR

Example [!NOTE] See issue

elcoosp · 4mo ago
kt3k
fix: use cli args correctlyMergedPR
kt3k · 4mo ago
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 (9mo ago). Open PRs: 0, open issues: 6. Last activity: 9mo ago. Community health: 50%. Top contributors: kt3k, eser, dkolba, denobot, elcoosp.

·@ofershap

Replace github.com with gitshow.dev