You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a swarm owner, I should be able to tie my swarm-pack deployment to a specific version (or semver pattern) of a swarm-pack, so that I can avoid surprises during updates.
With v2 swarm-pack it will be possible to target specific versions of a swarm-pack. Actually it was possible with v1 but there was no concept of a repo with multiple versions... This story relies on SP v2.
The text was updated successfully, but these errors were encountered:
As a swarm owner, I should be able to tie my swarm-pack deployment to a specific version (or semver pattern) of a swarm-pack, so that I can avoid surprises during updates.
With v2 swarm-pack it will be possible to target specific versions of a swarm-pack. Actually it was possible with v1 but there was no concept of a repo with multiple versions... This story relies on SP v2.
The text was updated successfully, but these errors were encountered: