Skip to content

refactor: 📝 explain about release process more in CHANGELOG #132

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

Merged
merged 4 commits into from
Nov 17, 2025
Merged

refactor: 📝 explain about release process more in CHANGELOG #132

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
a75a0c5
refactor: :memo: explain about release process more in CHANGELOG
lwjohnst86 Nov 7, 2025
c377c3c
refactor: :pencil2: small edits from review
lwjohnst86 Nov 13, 2025
1cb1e1c
Merge branch 'main' of https://github.com/seedcase-project/template-w…
lwjohnst86 Nov 14, 2025
269e049
refactor: :memo: match changes between CHANGELOGs
lwjohnst86 Nov 14, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 11 additions & 5 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,18 @@

Since we follow [Conventional
Commits](https://decisions.seedcase-project.org/why-conventional-commits),
we're able to automatically create a release with
we're able to automatically create formal "releases" of the website
based on our commit messages. Releases in the context of websites are
simply snapshots in time of the website content. We use
[Commitizen](https://decisions.seedcase-project.org/why-semantic-release-with-commitizen)
based on the commit messages. This means that releases can happen quite
often, sometimes several in a day. It also means any individual release
will not have many changes within it. Below is a list of releases along
with what was changed within it.
to automatically create these releases using
[SemVer](https://semverdoc.org) as the version numbering scheme.

Because releases are created based on commit messages, a new release is
created quite often---sometimes several times in a day. This also means
that any individual release will not have many changes within it. Below
is a list of the releases we've made so far, along with what was changed
within each release.

## 0.17.9 (2025-11-07)

Expand Down
16 changes: 11 additions & 5 deletions template/CHANGELOG.md
View file
Open in desktop
Copy link
Member

@signekb signekb Nov 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same comments as above ⏫

Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,15 @@

Since we follow [Conventional
Commits](https://decisions.seedcase-project.org/why-conventional-commits),
we're able to automatically create a release with
we're able to automatically create formal "releases" of the website
based on our commit messages. Releases in the context of websites are
simply snapshots in time of the website content. We use
[Commitizen](https://decisions.seedcase-project.org/why-semantic-release-with-commitizen)
based on the commit messages. This means that releases can happen quite
often, sometimes several in a day. It also means any individual release
will not have many changes within it. Below is a list of releases along
with what was changed within it.
to automatically create these releases using
[SemVer](https://semverdoc.org) as the version numbering scheme.

Because releases are created based on commit messages, a new release is
created quite often---sometimes several times in a day. This also means
that any individual release will not have many changes within it. Below
is a list of the releases we've made so far, along with what was changed
within each release.
Loading