-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
🚧Add a new prep release setting #50
Labels
high-priority
High Priority
✨new-feature
New feature that does not exist
preview
Done while in preview
Milestone
Comments
CalvinWilkinson
added
high-priority
High Priority
preview
Done while in preview
✨new-feature
New feature that does not exist
labels
Sep 20, 2024
CalvinWilkinson
added a commit
that referenced
this issue
Oct 2, 2024
CalvinWilkinson
added a commit
that referenced
this issue
Oct 2, 2024
* Start work for issue #50 * feat: add setting to trim the start of version used for prep releases * chore: add code docs * refactor: remove unused async await keywords * config: create deno task for linting * refactor: change code to meet coding standards * ci: improve format and lint status check workflows
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
high-priority
High Priority
✨new-feature
New feature that does not exist
preview
Done while in preview
Complete The Item Below
Description
Add a new setting to the prepare release config settings and process whose values will contain the string of characters to be trimmed from the start of the version.
An excellent example of this is for software where the character
v
is not allowed as the first character for a version string when updating the version. One example is Tauri. Tauri enforces semantic versioning but does not allow the version to start with the letterv
trimFromStartOfVersion
Acceptance Criteria
The items to complete to satisfy the Definition of Done.
ToDo Items
The items to complete to satisfy the Definition of Done.
Issue Dependencies
No response
Related Work
No response
Additional Information:
Unit Tests
Reasons for local unit test execution:
💡Warning💡
If the unit tests pass remotely and are not executed locally, this means we could be letting a bug slip into production.
Though bugs will always exist in some capacity, we should all do our part to help prevent them from happening.
Change Type Labels
🐛bug
🧨breaking-changes
✨new-feature
♻️cicd
⚙️config
🏎️performance
🗒️documentation/code
📝documentation/product
Priority Type Labels
low priority
medium priority
high priority
Code of Conduct
The text was updated successfully, but these errors were encountered: