mscharley / mscharley/dependency-changesets-action
Feature Request: support other package managers rather than package.json (dependabot)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 30
- Forks
- 7
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
I've been using this action to automatically generate chagesets for affected packages with dependabot.
- workflow for automated changesets: https://github.com/ladesa-ro/domain/blob/0c06070a8495db0764dfb8b30c5c9e030c9ecc10/.github/workflows/dependabot-changesets.yml
- dependabot config: https://github.com/ladesa-ro/domain/blob/0c06070a8495db0764dfb8b30c5c9e030c9ecc10/.github/dependabot.yml
It's works fine for dependabot updates that are specific for node/bun projects, to be specific, the changes made to package.json.
But i've been using changesets and dependabot with a monorepo with bun + dotnet project. So, my monorepo has the following structure:
-
defintions/package.json (bun)
-
integrations/typescript/package.json (bun)
-
integrations/dotnet
- package.json (only for track version)
- sln/project/project.csproj
the issue
when i got a dependabot update for integrations/dotnet/sln/project/project.csproj, mscharley/dependency-changesets-action do not detect the change, since the package.json do not have changed.
failed pr example: https://github.com/ladesa-ro/domain/pull/95
the proposal
i do propose an toggle feature that only works when the input detect-strategy: affected-package-dir is set.
with this option, if the subdirectory of a changesets project has some changes, it will be included, even if the package.json don't change
this is the current changeset status logic
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the affected-package-dir detect strategy and the referenced Changesets packages/git/src/index.ts range, then reproduce the linked failed PR using the .github workflow and dependabot configuration. Done means changes under a changesets project subdirectory are detected even when its package.json is unchanged, behind the proposed toggle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, devtools, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100