Skip to content

chore(release): 0.4.0 - #22

Merged
IamCoder18 merged 1 commit into
mainfrom
chore/release-0.4.0
Nov 17, 2026
Merged

IamCoder18 merged 1 commit into
mainfrom
chore/release-0.4.0

Conversation

@IamCoder18

@IamCoder18 IamCoder18 commented Nov 17, 2026 •

Copy link
Copy Markdown
Owner

Bumps the version to 0.4.0 and moves the Unreleased changelog section into a dated 0.4.0 entry.

Changes

  • cmd/root.go: Version 0.3.0 → 0.4.0
  • CHANGELOG.md: ## [Unreleased] → ## [0.4.0] - 2026-11-17, a fresh empty Unreleased section, and updated compare links.

Testing

  • go build ./...
  • go vet ./...
  • go test ./...

Summary by Sourcery

Release version 0.4.0 with dated changelog metadata and updated version reporting.

Enhancements:

  • Finalize the 0.4.0 release metadata and changelog entry.

Chores:

  • Update the CLI-reported version to 0.4.0 and reset the Unreleased changelog comparison links.

Bump the version to 0.4.0 and move the Unreleased changelog section
into a dated 0.4.0 entry.
@sourcery-ai

sourcery-ai Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

Reviewer's Guide

UI

Bump the version reported by the CLI to 0.4.0 for this release.

  • cmd/root.go L23

Documentation

Record the 0.4.0 release date and update the changelog comparison links while opening the next Unreleased section.

  • CHANGELOG.md L9-10, L662-663

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@kody-ai

kody-ai Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

Kody Review Complete

Great news! 🎉
No issues were found that match your current review configurations.

Keep up the excellent work! 🚀

Kody Guide: Usage and Configuration
Interacting with Kody
  • Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

  • Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

  • Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration
Review Options

The following review options are enabled or disabled:

Options Enabled
Bug ✅
Performance ✅
Security ✅
Business Logic ✅

Access your configuration settings here.

​

@coderabbitai

coderabbitai Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The changelog adds the 0.4.0 release heading and comparison link. The root command’s reported version changes from 0.3.0 to 0.4.0.

Changes: 0.4.0 Release Version

Layer / File(s) Summary
Update release metadata
CHANGELOG.md, cmd/root.go
The changelog adds the 0.4.0 release heading and comparison link. The root command reports version 0.4.0.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: Minimal · up to 71315

This release metadata change bumps the CLI version to 0.4.0 and updates the changelog. No merge-blocking risk was identified.

Pre-merge checks: Passed 4

Check name Status Explanation
Title check Passed The title "chore(release): 0.4.0" matches the main change: the version is bumped from 0.3.0 to 0.4.0 in cmd/root.go, and the CHANGELOG gets a dated 0.4.0 release entry. It is short and conventional-co…
Description check Passed The description states the version bump to 0.4.0 and the move of the Unreleased changelog section into a dated 0.4.0 entry. It also lists the changed files (cmd/root.go and CHANGELOG.md) and the build…
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.
Full details: Title check

Explanation

The title "chore(release): 0.4.0" matches the main change: the version is bumped from 0.3.0 to 0.4.0 in cmd/root.go, and the CHANGELOG gets a dated 0.4.0 release entry. It is short and conventional-commit style, though it does not say which files changed.

Full details: Description check

Explanation

The description states the version bump to 0.4.0 and the move of the Unreleased changelog section into a dated 0.4.0 entry. It also lists the changed files (cmd/root.go and CHANGELOG.md) and the build, vet, and test commands run. It is directly related to the changeset.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: bef9a53d-98f9-471b-a5a7-845121642ef4
Commits

Reviewing files that changed from the base of the PR and between eb6581a and 7131502.

Files selected for processing: 2

  • CHANGELOG.md
  • cmd/root.go

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

Recent review details

Context from checks skipped due to timeout: 3

  • GitHub Check: CodeRabbit
  • GitHub Check: Sourcery review
  • GitHub Check: Kody Code Review
Additional context used

Code guidelines: 2

AGENTS.md — auto-discovered
CONTRIBUTING.md — auto-discovered
Path-based instructions: 2

Source excerpt: [ ] CHANGELOG.md updated under `[Unreleased]`.

CodeRabbit inference engine (AGENTS.md)

Files:

  • CHANGELOG.md
Applicability reference: AGENTS.md: # AGENTS.md — guide for AI coding agents **No comments unless the user asked for them.**

CodeRabbit inference engine (CONTRIBUTING.md)

Files:

  • cmd/root.go

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

No issues found across 2 files

Turn on auto-fix | Re-trigger cubic

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Hey - I've found 1 issue

Prompt for AI Agents
Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="cmd/root.go" line_range="23" />
<code_context>
 	Use:     "schooltools",
 	Short:   "CLI tools for CBE / D2L / Brightspace",
-	Version: "0.3.0",
+	Version: "0.4.0",
 }

</code_context>
<issue_to_address>
**Release instructions reuse old tag**

When a maintainer copies the documented release commands for this release, a maintainer following the documented tagging commands literally creates the `v0.3.0` tag for the new release, so the release workflow publishes artifacts under the wrong version.

Update the example to `v0.4.0` or replace the concrete version with a clearly marked placeholder.
</issue_to_address>

Sourcery assessment

Approval pending. 1 finding to address first.

Blocking findings: cmd/root.go:23


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

Comment thread cmd/root.go
Use: "schooltools",
Short: "CLI tools for CBE / D2L / Brightspace",
Version: "0.3.0",
Version: "0.4.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 Medium · Release instructions reuse old tag

When a maintainer copies the documented release commands for this release, a maintainer following the documented tagging commands literally creates the v0.3.0 tag for the new release, so the release workflow publishes artifacts under the wrong version.

Update the example to v0.4.0 or replace the concrete version with a clearly marked placeholder.

Prompt for AI agents
In `cmd/root.go` at line 23:

**Release instructions reuse old tag**

When a maintainer copies the documented release commands for this release, a maintainer following the documented tagging commands literally creates the `v0.3.0` tag for the new release, so the release workflow publishes artifacts under the wrong version.

Update the example to `v0.4.0` or replace the concrete version with a clearly marked placeholder.

@IamCoder18
IamCoder18 merged commit bc491e3 into main Nov 17, 2026
9 checks passed
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