-
-
Notifications
You must be signed in to change notification settings - Fork 8
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
Use variables (including Version) with multiple packages #988
Comments
For single packages, this would work today: [[workflows]]
name = "print-version"
[[workflows.steps]]
type = "Command"
command = "echo $version"
variables = { "$version" = "Version" } For multi-package setups, we'd have to decide on something new. We really need a way to use variables with multiple packages anyway 😅. Would you want all versions in a single workflow (output with JSON maybe?) or run a specific workflow to get a specific package version? |
(I guess my suggestion is exactly what you had in #885) |
I completely forgot I had asked for that, and didn't see it in the issues list when I searched 😅 |
I've updated the issue title & description accordingly. |
There should be a way to use Knope's variables, including Version, with multiple packages.
[old description]
Since determining the version of a package is nontrivial, and it's often useful in scripts (e.g. in CI), I think it would be a great feature if Knope could detect the current version(s) of packages and print that, without doing anything else.
Users could probably parse this information out of
knope release --dry-run
, but that's a bit awkward.The primary use case I'm thinking of is to replace stuff like
git describe --abbrev=0 --tags | sed 's/v//'
, so the output must be easy to parse. For a standard, single package, it could just print the version it finds; for multiple packages, it could print<name>=<version>
, one on each line. Just likerelease
, when a package has multiple versioned files and their versions don't match, it should just print an error of some kind.The text was updated successfully, but these errors were encountered: