Not quite a problem, but as we start to have package registry, it's always manually (or using sedish tools) to update the version of a package.
Proposed Solution
scarb release replace 1.0.1, with a command like this or similar, we could have Scarb handling the version bumping, easy to integrated in CI that prepare new releases for instance.
In case of workspaces (if any package in the workspace), only this version should be updated, as some packages in the workspace may have their dedicated version voluntarily.
Problem
Not quite a problem, but as we start to have package registry, it's always manually (or using
sed
ish tools) to update the version of a package.Proposed Solution
scarb release replace 1.0.1
, with a command like this or similar, we could have Scarb handling the version bumping, easy to integrated in CI that prepare new releases for instance.In case of workspaces (if any package in the workspace), only this version should be updated, as some packages in the workspace may have their dedicated version voluntarily.
Notes
No response