ci: auto-generate-changelogs #376
Conversation
I propose we do time based releases, just for the sake of it, since we already deploy at every commit
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@teolemon do we need semantic versioning for a project like this? I mean, we could have a "stable" branch and regularly merge from main / devel. We don't need to add complexity with semantic versioning as we have no users (in terms of API). |
|
no semver needed, it's more regularly release. The only goal is to generate changelogs, create excitement, and post the novelties in slack @VaiTon |
|
Does this really make sense? Feels like one of these things that we have on the main website/repo so we are trying to clone it to this without having an actual need for it. |
Oh that's right with me, but I don't like GitHub releases with semver versioning. Is there any way to change that? |
|
Related discussion: |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| runs-on: ubuntu-latest | ||
| steps: | ||
| - id: release | ||
| uses: googleapis/[email protected] |
Check warning
Code scanning / CodeQL
Unpinned tag for a non-immutable Action in workflow Medium
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
What