Publish workflow can re-upload previous versions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.4k
- Forks
- 215
- Avg merge
- 2h 9m
- Merged PRs (30d)
- 27
Description
See https://github.com/winglang/wing/actions/runs/6312556360/job/17140355016
The commit contained no changes to the npm packages but it built a new package anyways. This seems to cause a problem when publishing to npm, where the version is different but the contents are the same. It's also generally wasteful to publish a new package if nothing changed.
We should skip publishing to npm if the winglang package (or any of its deps) have not changed.
Contributor guide
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 by inspecting the publish workflow referenced by the issue and the job from the linked GitHub Actions run. Trace how the winglang npm package and its dependencies are built and published; done means a commit with no package changes skips publishing while relevant changes still publish correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100