Skip to content

chore: begin 0.7.0.dev0 + backmerge main into dev (post-0.6.1) - #218

Merged
wjduenow merged 3 commits into
devfrom
chore/post-0.6.1-backmerge
Jun 11, 2026
Merged

chore: begin 0.7.0.dev0 + backmerge main into dev (post-0.6.1)#218
wjduenow merged 3 commits into
devfrom
chore/post-0.6.1-backmerge

Conversation

@wjduenow

@wjduenow wjduenow commented Jun 11, 2026

Copy link
Copy Markdown
Owner

Post-release housekeeping for v0.6.1:

  • Backmerge main (v0.6.1) into dev — fast-forward, since the release PR brought all of dev's brand-CLI content into main; main = dev + the release-prep commit.
  • Restore __version__ + skill metadata to 0.7.0.dev0 (next-dev keeps the 0.7 line — 0.6.1 was an interim patch; the Airflow operator remains 0.7.0).
  • CHANGELOG is in main's post-release shape: empty [Unreleased] + dated [0.6.1] section (clears dev's promoted carryover, so next release's stale-[Unreleased] guard stays clean).

Validation: ruff / format / pyright / pytest (3809 passed) all green.

Summary by CodeRabbit

  • Chores
    • Updated changelog and version tracking information.

@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: cda5d14b-db0c-4d8f-b131-eda6bcb2ca8b

📥 Commits

Reviewing files that changed from the base of the PR and between bf8fce7 and c3d758a.

📒 Files selected for processing (1)
  • CHANGELOG.md

📝 Walkthrough

Walkthrough

The CHANGELOG.md is updated to establish v0.6.1 as a new release (dated 2026-06-11), add an "Unreleased" placeholder section for ongoing development on the dev branch, and update the GitHub compare link to use v0.6.1 as the baseline for unreleased changes.

Changes

Changelog Release Preparation

Layer / File(s) Summary
Unreleased section and v0.6.1 release header
CHANGELOG.md
Changelog adds "Unreleased" placeholder (entries land on dev) and new v0.6.1 release heading dated 2026-06-11; compare link updated from v0.6.0 to v0.6.1 baseline.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • wjduenow/SignalForge#174: Both PRs modify CHANGELOG.md with release header and compare link updates related to version cycles.
  • wjduenow/SignalForge#207: Both PRs adjust CHANGELOG.md "Unreleased" section and version baseline links for release management.

Poem

🐰 A changelog grows, release in sight,
v0.6.1 shines bold and bright!
The dev branch waits for notes to come,
Compare links dance, old version done. ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and specifically summarizes the main change: beginning version 0.7.0.dev0 and backmerging main into dev after the 0.6.1 release.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.


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

@wjduenow
wjduenow merged commit d99390e into dev Jun 11, 2026
6 checks passed
@wjduenow
wjduenow deleted the chore/post-0.6.1-backmerge branch June 11, 2026 15:35
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.

1 participant