Increment version to 3.6.2

[JensAstrup]

What's Changed

Tested

• [x] View and Interact with Todoist buttons
  • [x] View Story page with Todoist disabled
• [x] Use both analyze and break down AI features
  • [x] With proxy
  • [ ] Without proxy
• [x] View development time for in progress stories
  • [x] On page load
  • [x] On SPA navigation
• [x] View cycle time on a completed story
  • [ ] On page load
  • [ ] On SPA navigation
• [ ] Add notes to a story

Summary by CodeRabbit

• New Features

  • Updated version to 3.6.2 in the application and manifest files.

• Chores

  • Incremented versioning information for better tracking and release management.

[coderabbitai[bot]]

Walkthrough

The changes involve updating versioning information across two files: the .env file and the src/manifest.json file. The VERSION and SENTRY_RELEASE variables in the .env file have been incremented from 3.6.1 to 3.6.2, while the CHANGELOG_VERSION remains at 3.0.1. In the src/manifest.json, the version number is also updated from "3.6.1" to "3.6.2". No other modifications were made to the functionality or structure of the files.

Changes

File	Change Summary
.env, src/manifest.json	Version updated from 3.6.1 to 3.6.2 for both VERSION and SENTRY_RELEASE in .env and for the "version" field in src/manifest.json.

Sequence Diagram(s)

---

:scroll: Recent review details

**Configuration used: CodeRabbit UI** **Review profile: ASSERTIVE**

:inbox_tray: Commits

Files that changed from the base of the PR and between d65d547db6c3e18adc8470d335f1b8edc4d7032e and 8b625acc3683df2c221a3e0fe653276937cf312b.

:ledger: Files selected for processing (2)

* .env (1 hunks) * src/manifest.json (1 hunks)

:mute: Additional comments not posted (5)

.env (4)

`1-1`: **Version increment looks good.** The VERSION has been correctly updated from 3.6.1 to 3.6.2, which aligns with the PR objective of incrementing the version. --- `3-3`: **SENTRY_RELEASE update is consistent.** The SENTRY_RELEASE has been updated to match the new VERSION (3.6.2), maintaining consistency in the versioning across different parts of the application. --- `2-2`: **Consider updating CHANGELOG_VERSION.** The CHANGELOG_VERSION remains at 3.0.1 while VERSION and SENTRY_RELEASE have been incremented. Consider whether this value should also be updated to reflect the new version. Could you please clarify the purpose of CHANGELOG_VERSION and confirm if it should remain at 3.0.1? --- Line range hint `1-11`: **Changes align with PR objectives.** The version increment in this file aligns with the PR objective of updating the project version to 3.6.2. However, please ensure that all the tests mentioned in the PR description (Todoist buttons, AI features, development time view, cycle time view, and adding notes to a story) have been conducted before merging this PR. Have all the tests mentioned in the PR description been completed? If not, please update the PR description with the current status of each test.

src/manifest.json (1)

`85-85`: **Version increment looks good.** The version has been correctly updated from 3.6.1 to 3.6.2, which aligns with the PR objectives. This minor version increment typically indicates bug fixes or small enhancements. As a reminder, please ensure that all items in the testing checklist mentioned in the PR description are completed: 1. View and interact with Todoist buttons (Story page with Todoist disabled) 2. Use both analyze and break down AI features (with and without proxy) 3. View development time for in-progress stories (on page load and SPA navigation) 4. View cycle time on completed stories (on page load and SPA navigation) 5. Add notes to a story These tests will help verify that the functionality works as expected in the new version.

---

:placard: Tips

### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , 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. ### CodeRabbit Configuration File (`.coderabbit.yaml`) - You can programmatically configure CodeRabbit by adding a `.coderabbit.yaml` file to the root of your repository. - Please see the [configuration documentation](https://docs.coderabbit.ai/guides/configure-coderabbit) for more information. - If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: `# yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json` ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](https://discord.com/invite/GsXnASn26c) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.

[github-actions[bot]]

This commit contains updates to the application's version and configuration setup in two files: .env and src/manifest.json. Here's an overview of the changes and some feedback:

1. .env Changes:

   • The VERSION and SENTRY_RELEASE variables have been updated from 3.6.1 to 3.6.2.
   • The CHANGELOG_VERSION remains unchanged at 3.0.1.
   • No changes have been made to GOOGLE_MEASUREMENT_ID or the PROXY_URL and PROXY_OPENAI_URL.

2. src/manifest.json Changes:

   • The version number within the manifest.json file has been updated from 3.6.1 to 3.6.2, ensuring consistency with the version update in the .env file.

Positive Feedback:

• Consistency: Updating the version numbers in both the configuration and manifest files ensures consistency across the application's metadata and its deployment configuration. This is crucial for maintaining accurate version tracking and compatibility, especially in environments that rely on version number accuracy for caching, releases, or rollback procedures.
• Sentry Integration: Keeping the SENTRY_RELEASE version synchronized with the application version is an excellent practice. It improves the accuracy of error reporting and aids in debugging by matching errors with the specific release in which they occur.

General Recommendation:

• Version Updates: It's good practice to keep version updates in dedicated commits. This commit is a clean example of that, making it straightforward for any team member (or automation tools) to track version changes without sifting through unrelated modifications.
• Documentation: Whenever version changes occur, it's beneficial to include notes in the commit message or an accompanying documentation update that outlines any significant changes or reasons for the version increment. This practice wasn't directly observed here but is a general recommendation for future work.

Overall, these changes are clear, well-structured, and follow best practices for version management and application configuration updates.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.36%. Comparing base (d65d547) to head (8b625ac). Report is 1 commits behind head on develop.

Additional details and impacted files

[](https://app.codecov.io/gh/JensAstrup/shortcut-assistant/pull/501?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Jens+Astrup) ```diff @@ Coverage Diff @@ ## develop #501 +/- ## ======================================== Coverage 93.36% 93.36% ======================================== Files 58 58 Lines 1206 1206 Branches 182 178 -4 ======================================== Hits 1126 1126 Misses 75 75 Partials 5 5 ```