Comments (2)
it resets the old content, runs changeset bump and pushes again.
Really like this as a solution to automating the bump process - it being a bit clunky has been annoying me (the number of round trips you need to make)
exposing npm credentials would be really really bad
Someone had a moderately okay solution to this which basically ferried the 2fa request to a slack bot and then back when you run release. Changesets would need to support post-hoc 2fa entry though (working on it).
This keeps 2fa while still having mostly-automated releases.
Maybe this doesn't help because it adds another step.
This is a good idea, and effectively what we do in Atlaskit. The always-around new-release branch helps out a lot (if all I got was that and still had to merge, pull, publish, I would be significantly happier with my life).
You may want to lock down who can merge the release branch further, but that's an easy implementation detail.
from changesets.
This has been done by https://github.com/changesets/action - closing
from changesets.
Related Issues (20)
- `pkg:changeset-cli` `changeset status --since=main` not detecting new changesets in PR HOT 1
- `pkg:cli` Flag for publish command to only publish a snapshot version
- Make 'Changeset detected' look more different from 'No Changeset found' HOT 1
- `yarn version`: `Unknown Syntax Error: Not enough positional arguments.` HOT 1
- cant publish new version from within a github action HOT 1
- `pkg:cli` missing `./bin.js` in exports HOT 6
- Wrong formatting of summary text HOT 1
- [feat] `@changesets/cli` Ability to publish on different registries at once HOT 1
- [IDEA]: `changeset publish` should fail if `access: 'restricted'` yet package is currently public
- [`@changesets/cli`] publish via `yarn` berry is not supported
- [FR] changeset status --only
- Changesets ran into trouble committing your files (CI only) HOT 1
- Version Bump not as expected HOT 6
- Action succeeds but package is never published to npm HOT 1
- CHANGELOG.md change lists unwanted formatting. HOT 6
- `changset tag` tags every project in monorepo with every project's tags
- [@changesets/cli] `publish` cannot detect already published package when "latest" tag doesn't exist
- Unexpected package version
- There is a risk of inadvertently creating incorrect major version
- changeset tag doesn't point to a commit
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from changesets.