Skip to content

Automation rules: support for updating version slug #12128

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.

Sign up for GitHub

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

Jump to bottom
Open
agjohnson opened this issue Apr 23, 2025 · 0 comments
Open

Automation rules: support for updating version slug #12128

agjohnson opened this issue Apr 23, 2025 · 0 comments
Labels
Feature New feature Needed: design decision A core team decision is required

Comments

@agjohnson
Copy link
Contributor

This might be at the limit of what editable versions were meant for, but it would be really nice to be able to have automation rules add version slugs so that users could have a rule like:

  • 4\..* matching versions follow semantic versioning and the latest gets custom slug 4.0
  • 3\.3\..* matching versions follow semantic versioning and the latest gets custom slug 3.3
  • 2\..* matching versions follow semantic versioning and the latest gets custom slug 2.0

The issue is maybe in removing the previous custom slug however, ie:

  • Before, version 2.2.2 has custom slug 2.0
  • After, version 2.3.0 has custom slug 2.0 and version 2.2.2 has custom slug reverted/removed
@agjohnson agjohnson added Needed: design decision A core team decision is required Feature New feature labels Apr 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Feature New feature Needed: design decision A core team decision is required
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@agjohnson