Closed greenkeeper[bot] closed 6 years ago
Update to this version instead π
post: create v1.2.3
tag tag instead of branch (3f85597)
Note that if a version was released with v7.0.1, you will run into the ENOTINHISTORY
error :( To recover, follow these steps:
"version"
to what ever should have been released. As an example, let's say the new version number would be 1.2.3
. Save the changenpm publish
to release the new version. Make sure to run any pre-publish tasks first if you have anygit tag v1.2.3
(put in the same version as in step 2. Push the tag to GitHub with git push --tags
This will fix the problem and everything will work automagically again from here on now.
Update to this version instead π
The new version differs by 4 commits.
8c44c31
fix(package): update @semantic-release/commit-analyzer to version 3.0.1
dd60b46
fix(package): update @semantic-release/release-notes-generator to version 4.0.0
88b5895
docs(README): update commit lint suggestion (#429)
1ceae83
docs(troubleshooting): initial version (#399)
See the full diff
Update to this version instead π
The new version differs by 4 commits.
9951cf7
fix(package): Set minimum node version to 4 (#442)
2d14c53
fix(package): update @semantic-release/last-release-npm to version 2.0.0
277d9ab
chore(package): update cz-conventional-changelog to version 2.0.0
4612a05
chore(package): update commitizen config
See the full diff
Update to this version instead π
The new version differs by 16 commits.
580ad9c
feat: Allow to recover from ENOTINHISTORY with a tag and handle detached head repo
8e9d9f7
fix: Always pass pluginConfig to plugins as a defined object
90417c6
fix: Exit with 1 if unexpected error happens
85dd69b
feat: Retrieve version gitHead from git tags and unshallow the repo if necessary
cbb51a4
ci(codecov): Set default branch in codecov.yml
a58d12d
chore: Update badges
42b3382
ci(travis): Update .travis.yml
cc3c8f2
ci: Use codecov for code coverage
abf92ad
refactor: Use ES6, Test with AVA
7fe0890
chore: Remove editorconfig
f10f157
chore: More generic .gitignore
(Windows, Mac OS, Linux)
40e296b
chore: Remove lockfiles
266a3f7
chore: Add license file
42456a3
chore(package): update coveralls to version 3.0.0
3a4334f
fix(package): update @semantic-release/error to version 2.0.0
There are 16 commits in total.
See the full diff
Version 7.0.1 of semantic-release just got published.
The version 7.0.1 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of semantic-release. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v7.0.17.0.1 (2017-08-14)
Bug Fixes
Commits
The new version differs by 9 commits.
3f85597
fix(post): Create a tag before makeing a release
f148a61
fix(post): fix target_commitish to be the default branch
5b3bdd2
chore: remove console.log
64d84a0
chore(travis): drop builds in Node <4
1fa6d50
fix(package): update @semantic-release/release-notes-generator to version 3.0.1
6145bc9
docs(readme): add sgc (#386)
609b46f
docs(README): minor typo (#376)
76cd99c
chore(package): update standard to version 9.0.0
22dc640
chore(package): update tap to version 10.0.1
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: