WIP chore: include chores and more prefixes in the changelog

[arealmaas]

Solving a part of this issue: #1461 Hopefully the release will be triggered when creating chores now too. All other settings are the default settings which matches the settings we had previously.

Summary by CodeRabbit

• New Features

  • Introduced a manifest file for release management, indicating the current project version (1.39.0).
  • Added a configuration file to streamline the release process with specified settings for changelog and release types.

• Improvements

  • Updated CI/CD workflow to enhance release categorization and deployment processes, including new parameters for Docker images and migration handling.

These enhancements will improve the release management workflow, ensuring clearer version tracking and configuration.

[coderabbitai]

📝 Walkthrough

📝 Walkthrough

Walkthrough

This pull request updates the release management configuration by modifying the existing .release-please-manifest.json file to reflect a new version string of "1.39.0". Additionally, it introduces a new configuration file, release-please-config.json, which defines the parameters for the release process. Furthermore, the CI/CD workflow in .github/workflows/ci-cd-main.yml has been updated to remove a parameter and add new parameters related to Docker image naming and migration handling.

Changes

File	Change Summary
.release-please-manifest.json	Updated version string from "0.0.0" to "1.39.0".
release-please-config.json	New configuration file added with settings for the release process, including changelog path and versioning rules.
.github/workflows/ci-cd-main.yml	Modified CI/CD workflow: removed release-type: simple, added dockerImageBaseName and runMigration, and updated job results for Slack notifications.

Possibly related PRs

• ci: ensure unique revisions for deployments #1211: The changes in the CI/CD workflow configuration in .github/workflows/action-deploy-apps.yml may relate to the main PR as they involve deployment processes, which could be affected by the versioning updates in the main PR.
• ci: ensure the check-for-changes checks previous deployed version #1346: This PR modifies the CI/CD workflow to ensure that the check-for-changes functionality verifies the previous deployed version, which is relevant to the version management aspect of the main PR.
• ci: ensure we store the versions as gh variables #1405: The focus on storing version information as GitHub variables in this PR directly relates to the versioning updates made in the main PR.
• ci: ensure version is stored when deploying apps #1481: This PR addresses the storage of version information during app deployments, which is closely tied to the version management changes in the main PR.

Suggested reviewers

• knuhau
• oskogstad

Warning

Rate limit exceeded

@arealmaas has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 17 minutes and 57 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between e7f8adb and 613b944.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between e7f8adb and 613b944.

📒 Files selected for processing (1)

• release-please-config.json (1 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• release-please-config.json

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[arealmaas]

After some discussion with @oskogstad we await this after we've discussed a bit more in detail