We've always wanted to increment minor versions instead of patch versions for new releases, as it's more semantic. This PR will change the snapshot version calculation to increment the minor number instead of the patch number. Came up from [this Slack thread](https://theappsmith.slack.com/archives/CGBPVEJ5C/p1705674928122129?thread_ts=1704793408.986219&cid=CGBPVEJ5C).
52 lines
1015 B
YAML
52 lines
1015 B
YAML
name-template: "Release v$RESOLVED_VERSION 🌈"
|
|
tag-template: "v$RESOLVED_VERSION"
|
|
categories:
|
|
- title: "🚀 Features"
|
|
labels:
|
|
- "Enhancement"
|
|
- title: "🐛 Bug Fixes"
|
|
labels:
|
|
- "Bug"
|
|
|
|
# Only include the following labels in the release notes. All other labels are ignored.
|
|
exclude-labels:
|
|
- "skip-changelog"
|
|
|
|
change-template: "- $TITLE (#$NUMBER)"
|
|
|
|
change-title-escapes: '\<*_&' # You can add # and @ to disable mentions, and add ` to disable code blocks.
|
|
|
|
version-resolver:
|
|
major:
|
|
labels:
|
|
- "Major"
|
|
minor:
|
|
labels:
|
|
- "Minor"
|
|
patch:
|
|
labels:
|
|
- "Patch"
|
|
default: minor
|
|
|
|
template: |
|
|
## What's new?
|
|
|
|
$CHANGES
|
|
|
|
# The below configurations will label our PRs automatically
|
|
# autolabeler:
|
|
# - label: "Chore"
|
|
# title:
|
|
# - "/chore/i"
|
|
# - "/docs/i"
|
|
# - label: "Test"
|
|
# title:
|
|
# - "/test/i"
|
|
# - label: "Bug"
|
|
# title:
|
|
# - "/fix/i"
|
|
# - label: "Enhancement"
|
|
# title:
|
|
# - '/feature\/.+/'
|
|
# - "/feat/i"
|