Decouple version determiner from npm registry #56
Assignees
Comments
|
👍 |
|
This is something I'd love to see. We could introduce another plugin hook "getLastRelease", leave the current implementation as default, and provide a git-tag based implementation. Anyone up for tackling this one? |
|
I'd love to try... I'm a little busy, But I'll try to get to it today or
tomorrow.
ᐧ
|
|
@ariporad This sounds fantastic, do you want to chat about it some more on gitter first? |
|
Alright, @ariporad will take a stab at implementing this 👍
🎉 |
ariporad
added a commit
to semantic-release/last-release-npm
that referenced
this issue
Aug 17, 2015
Moved the code out of core into it's own project. Previously: https://github.com/semantic-release/semantic-release/blob/77349fcdf193467967fa4a85daf2ee3fa812779b/src/lib/last-release.js Refs semantic-release/semantic-release#56, semantic-release/semantic-release#51
ariporad
added a commit
to ariporad/semantic-release
that referenced
this issue
Aug 17, 2015
Move getLastRelease into it's very own plugin (@semantic-release/last-release-npm), which this project now depends on. BREAKING CHANGE: Remove npmTag from output of getLastRelease. It wasn't used anywhere. Refs semantic-release#56, semantic-release#51
|
Number 1 is fixed in #57. |
|
👍 |
ariporad
added a commit
to semantic-release/last-release-git-tag
that referenced
this issue
Aug 20, 2015
Add all intended functionality: [x] Fully compatable with semantic-release 4.0.0 plugin API [x] Gets last version from git tag [x] Calls callback with an error or a proper release object Fixes semantic-release/semantic-release#56
Closed
This was referenced Nov 18, 2020
This was referenced Mar 30, 2021
This was referenced May 25, 2021
This was referenced Sep 16, 2021
Open
This was referenced Dec 31, 2021
Open
This was referenced Jan 16, 2022
This was referenced Jul 2, 2022
This was referenced Nov 29, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Last release is currently determined by consulting the npm registry. As mentioned (out of band), this could be made more flexible by looking at Git tags (for example).
A use case for this could be in situations where the
npm publishstep is undesirable. This seems to resonate with some of the discussion in #51.The text was updated successfully, but these errors were encountered: