v4.4.54 - start branch

[grzesir]

chore: start 4.4.54\n\n- bump setup.py to 4.4.54\n- add CHANGELOG unreleased header

Summary by CodeRabbit

• Chores
  • Version bumped to 4.4.54 and changelog updated in preparation for release.

[coderabbitai]

📝 Walkthrough

Walkthrough

Updates package version from 4.4.53 to 4.4.54 in setup.py and adds a new unreleased changelog section in CHANGELOG.md for tracking upcoming changes. Standard version release bookkeeping.

Changes

Cohort / File(s)	Summary
Version Bump CHANGELOG.md, setup.py	Updated package version from 4.4.53 to 4.4.54 and added new unreleased changelog section header.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• v4.4.43 - Hotfix: add_ohlc actually shipped #958: Both PRs are release bookkeeping that update setup.py's version argument and add a new CHANGELOG release header.

Poem

🐰 A version hops from three to four,
The changelog door opens once more,
New section waits for changes dear,
Release bookkeeping, crystal clear! 📝

🚥 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 'v4.4.54 - start branch' accurately reflects the main changes: bumping the version to 4.4.54 and starting a new release branch.
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 docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch version/4.4.54

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Pylint (4.0.5)

setup.py

************* Module pylintrc
pylintrc:1:0: F0011: error while parsing the configuration: File contains no section headers.
file: 'pylintrc', line: 1
'known-third-party=lumibot' (config-parse-error)
[
{
"type": "convention",
"module": "setup",
"obj": "",
"line": 1,
"column": 0,
"endLine": null,
"endColumn": null,
"path": "setup.py",
"symbol": "missing-module-docstring",
"message": "Missing module docstring",
"message-id": "C0114"
}
]

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

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`:
- Around line 3-4: Replace the placeholder heading "## 4.4.54 - Unreleased" with
the required release header format "## X.Y.Z - YYYY-MM-DD" and add the standard
empty section scaffolding (Added, Changed, Fixed, Deprecated, Removed, Security)
under that heading; if this is only a start-of-cycle placeholder instead of a
dated release, remove the versioned header or leave a single commented note and
only add the full "## X.Y.Z - YYYY-MM-DD" heading plus the six sections
(Added/Changed/Fixed/Deprecated/Removed/Security) when the release date is known
so the CHANGELOG.md complies with the project guideline.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 552a12c5-2b2d-448e-a636-dedb3907cdb6

📥 Commits

Reviewing files that changed from the base of the PR and between 6f1c9a6 and ae0c42a.

📒 Files selected for processing (2)

• CHANGELOG.md
• setup.py

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Keep the new changelog entry in the repo’s release format.

## 4.4.54 - Unreleased doesn’t match the required ## X.Y.Z - YYYY-MM-DD heading, and this new block is also missing the standard Added/Changed/Fixed/Deprecated/Removed/Security sections. If this is only a start-of-cycle placeholder, I’d either add the empty section scaffolding now or wait to add the versioned header until the release date is known.

As per coding guidelines, "Changelog format must use sections: Added, Changed, Fixed, Deprecated, Removed, Security, with date in format ## X.Y.Z - YYYY-MM-DD."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` around lines 3 - 4, Replace the placeholder heading "## 4.4.54
- Unreleased" with the required release header format "## X.Y.Z - YYYY-MM-DD"
and add the standard empty section scaffolding (Added, Changed, Fixed,
Deprecated, Removed, Security) under that heading; if this is only a
start-of-cycle placeholder instead of a dated release, remove the versioned
header or leave a single commented note and only add the full "## X.Y.Z -
YYYY-MM-DD" heading plus the six sections
(Added/Changed/Fixed/Deprecated/Removed/Security) when the release date is known
so the CHANGELOG.md complies with the project guideline.