Skip to content

[CHORE] sync dev with master after v1.13.1#409

Merged
aarmoa merged 12 commits intodevfrom
chore/sync_dev_with_master_after_v1_13_1
Mar 3, 2026
Merged

[CHORE] sync dev with master after v1.13.1#409
aarmoa merged 12 commits intodevfrom
chore/sync_dev_with_master_after_v1_13_1

Conversation

@aarmoa
Copy link
Collaborator

@aarmoa aarmoa commented Mar 3, 2026

  • Sync dev branch with the latest changes in master after v1.13.1 release

Summary by CodeRabbit

  • Chores
    • Updated project version to 1.14.0-rc1
    • Updated changelog with new version 1.14.0 entry

@aarmoa aarmoa requested a review from Copilot March 3, 2026 16:13
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 3, 2026

📝 Walkthrough

Walkthrough

The PR bumps the project version from 1.13.1 to 1.14.0-rc1 in pyproject.toml and adds a new 1.14.0 changelog entry with a placeholder date, preparing the codebase for the upcoming release.

Changes

Cohort / File(s) Summary
Release Preparation
CHANGELOG.md, pyproject.toml
Version bump to 1.14.0-rc1 and new changelog header with placeholder date (9999-99-99).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A version hops forth with mighty stride,
From one-point-thirteen to the new release tide,
RC-one arrives, the changelog gleams,
With placeholder dates and hopeful dreams!
✨ Onward to greatness, the rabbit team beams!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the PR objective of syncing the dev branch with master after v1.13.1 release, and is clear and specific about the main purpose.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/sync_dev_with_master_after_v1_13_1

Comment @coderabbitai help to get the list of available commands and usage tips.

@socket-security
Copy link

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedckzg@​2.1.510010090100100

View full report

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Syncs the dev branch with master post v1.13.1 by advancing the package version and preparing the changelog for the next release cycle.

Changes:

  • Bumped Poetry project version to 1.14.0-rc1.
  • Added a new 1.14.0 section to CHANGELOG.md as a placeholder for upcoming release notes.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
pyproject.toml Updates the package version for the next release iteration.
CHANGELOG.md Adds a new top-level release section for 1.14.0.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[tool.poetry]
name = "injective-py"
version = "1.13.1"
version = "1.14.0-rc1"
Copy link

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

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

tool.poetry.version must be a valid PEP 440 version. 1.14.0-rc1 is typically rejected by Python packaging tooling (expects 1.14.0rc1 for a release candidate), which can break poetry build/publish and downstream installs.

Suggested change
version = "1.14.0-rc1"
version = "1.14.0rc1"

Copilot uses AI. Check for mistakes.
[tool.poetry]
name = "injective-py"
version = "1.13.1"
version = "1.14.0-rc1"
Copy link

Copilot AI Mar 3, 2026

Choose a reason for hiding this comment

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

The version in pyproject.toml (1.14.0-rc1) doesn’t match the new CHANGELOG header (1.14.0). If this is an RC, consider keeping the CHANGELOG section version consistent (or use an unreleased section until the final 1.14.0 cut).

Copilot uses AI. Check for mistakes.
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Line 5: Replace the non-standard placeholder date in the changelog header "##
[1.14.0] - 9999-99-99" with a conventional marker; update that header to use
"Unreleased" (preferred) or "TBD" instead of "9999-99-99" so it reads e.g. "##
[1.14.0] - Unreleased", keeping the rest of the line intact.

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9569c6c and a329fe5.

📒 Files selected for processing (2)
  • CHANGELOG.md
  • pyproject.toml


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

## [1.14.0] - 9999-99-99
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Replace the non-standard placeholder date.

The placeholder date "9999-99-99" is unconventional and could cause confusion. Standard changelog conventions recommend using "Unreleased" or "TBD" for versions in development.

📝 Suggested alternatives

Option 1 (recommended): Use "Unreleased" following keepachangelog.com convention

-## [1.14.0] - 9999-99-99
+## [1.14.0] - Unreleased

Option 2: Use "TBD" placeholder

-## [1.14.0] - 9999-99-99
+## [1.14.0] - TBD
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## [1.14.0] - 9999-99-99
## [1.14.0] - Unreleased
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` at line 5, Replace the non-standard placeholder date in the
changelog header "## [1.14.0] - 9999-99-99" with a conventional marker; update
that header to use "Unreleased" (preferred) or "TBD" instead of "9999-99-99" so
it reads e.g. "## [1.14.0] - Unreleased", keeping the rest of the line intact.

@aarmoa aarmoa changed the base branch from master to dev March 3, 2026 16:18
@aarmoa aarmoa merged commit 33cd59e into dev Mar 3, 2026
18 checks passed
@aarmoa aarmoa deleted the chore/sync_dev_with_master_after_v1_13_1 branch March 3, 2026 16:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants