chore: tagged v27 changelog

[crnbarr93]

What is the purpose of the change

Updates changelog for v27.0.0 release

[coderabbitai]

Walkthrough

The pull request introduces a new version entry v27.0.0 in the CHANGELOG.md file, categorized under "State Breaking," "Config," and "State Compatible." It details updates to dependencies, fixes for state exports related to the governance module, and improvements in logging for superfluid operations. Additionally, it highlights the addition of missing proto files and new queries in the x/gauges module. The changelog is organized according to semantic versioning principles and includes a comparison to the previous version v26.0.1.

Changes

File	Change Summary
CHANGELOG.md	Added new version entry ## v27.0.0 with sections for "State Breaking," "Config," and "State Compatible." Included updates on dependencies, state export fixes, new features, and concurrency improvements.

Possibly related PRs

• fix: supply offsets for osmo token #8751: This PR addresses fixes for supply offsets related to the osmo token, which is mentioned in the main PR's changelog update for version v27.0.0.
• fix: state export for gov module constitution #8777: This PR fixes state export issues for the governance module constitution, which is also highlighted in the main PR's changelog for version v27.0.0.
• chore: bump cometbft/cosmos-sdk versions #8779: This PR involves bumping the versions of cometbft/cosmos-sdk, which is noted in the main PR's changelog update for version v27.0.0.

Suggested labels

V:state/breaking, C:app-wiring

Suggested reviewers

• czarcas7ic
• PaddyMc
• nicolaslara

---

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.

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 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 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (5)

CHANGELOG.md (5)

Line range hint 1-24: Documentation format needs improvement

The changelog header section should include:

1. A clear statement of supported Go versions
2. Minimum supported node requirements
3. Any critical upgrade requirements

Consider adding this information in a standardized header section.

# Changelog

All notable changes to Osmosis will be documented in this file.

## Supported Environments
- Go version: 1.21+
- Node requirements: {cpu, ram, disk specs}

## Critical Upgrade Notes
- Node operators must...
- API users should...

---

Line range hint 45-85: Breaking changes need more migration guidance

The v27.0.0 state breaking changes section lists significant changes but lacks sufficient migration guidance for:

• Smart account module activation
• ProtoRev distribution changes
• Changes to gauge creation requirements

Consider adding a "Migration Guide" subsection under each major version that details required actions for node operators, API consumers, and smart contract developers.

---

Line range hint 86-150: Inconsistent PR reference format

The changelog has inconsistent formatting for PR references:

• Some use full URLs: [#8682](https://github.com/osmosis-labs/osmosis/pull/8682)
• Others use just PR numbers: [#8734]
• Some lack descriptions of the actual changes

Standardize on full URLs with descriptive text of the changes.

* [#8734](https://github.com/osmosis-labs/osmosis/pull/8734) Update CosmWasm VM to latest version to improve contract execution performance and security

---

Line range hint 151-200: Add impact assessment for security updates

Security-related changes should include:

1. Severity level
2. Potential impact
3. Whether user action is required
4. Timeline for required actions

This helps users properly prioritize updates.

### Security

* [#8777](https://github.com/osmosis-labs/osmosis/pull/8777) CRITICAL: Fix state export for gov module constitution
  - Severity: Critical
  - Impact: Could lead to incorrect governance state after chain export
  - Action Required: Node operators must upgrade before block X
  - Timeline: Must be completed by YYYY-MM-DD

---

Line range hint 201-250: Improve version comparison documentation

For major version changes (like v26 to v27), add a high-level summary section that outlines:

1. Key new features and capabilities
2. Breaking changes summary
3. Performance impact
4. Required configuration changes

This helps users quickly understand the impact of the upgrade.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between e942fde and dd5915e.

📒 Files selected for processing (1)

• CHANGELOG.md (1 hunks)

[niccoloraspa]

LGTM