New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom bump commit message #230
Comments
I might prefer no bump commits (like {
"skipBumpCommit": true
} With bump commits disabled, the latest NPM version is the source of truth (or maybe it already works that way?) and the "version" field in |
is skip CI different on travis? without that in your commit messages you can easily fall into a loop |
|
I'm not actually sure. If it's required in the commit header, then so be it. 😆
Oh really? Nice. Is no bump commit created in that case? |
No in that case we bump the published version cause you can publish over an old version. I'm having trouble visualizing how |
What do you think of |
|
Two options if thats what you want:
|
A package with a version of
When a new NPM version should be published, Auto should increment the "current version" using The changelog uses the "current version" from NPM (instead of from As always, a new Github release is created for every NPM version. Am I being clear enough? |
To publish new versions to NPM you have to change this. The only way to increment the "current version" and never change the local one would be to:
I'm pretty sure I understand your use case. a. you don't want to publish a bunch of versions while you are developing a feature over multiple PRS In my eyes we already give you two ways to do this:
How does this differ from the behavior you want? It seem to me to boil down to: you want to add |
to accomplish my last sentence you could probably make a plugin that uses The only problem I see with this is that it would also fail the CI job. |
Interesting interpretation, but not quite what I intended. 😅 I'm basically describing how I should have said "The version in |
Ok so the state you would end up in is: repo: only ever has verison 0.0.0-dev npm: Has the real version all the time (this is whats used for anything) correct? |
Kinda like if (auto.options.skipBumpCommit) {
// get published version
// change local version to publish
} else {
await execPromise('npm', [
'version',
latestBump || version,
'-m',
'"Bump version to: %s [skip ci]"'
]);
}
await setTokenOnCI();
await execPromise(
'npm',
!isPrivate && isScopedPackage
? ['publish', '--access', 'public']
: ['publish']
);
if (auto.options.skipBumpCommit) {
// change local version back to DEV
}
await execPromise('git', [
'push',
'--follow-tags',
'--set-upstream',
'origin',
'$branch'
]);
} |
Yeah, looks good! |
|
If you want, you could bake this feature into Auto for now, and wait to split the |
This should be possible via plugin now with #247 (the semver ability). The commit message thing requires a bit of config changes and doesn't really get you much. Closing but open to PRs! |
Feature: Add an
.autorc
option for customizing the commit message used by the NPM plugin when it bumps the package version.The text was updated successfully, but these errors were encountered: