Repository navigation
chore(release): 0.4.0 - #22
Conversation
Bump the version to 0.4.0 and move the Unreleased changelog section into a dated 0.4.0 entry.
Reviewer's GuideUIBump the version reported by the CLI to 0.4.0 for this release.
DocumentationRecord the 0.4.0 release date and update the changelog comparison links while opening the next Unreleased section.
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Kody Review CompleteGreat news! 🎉 Keep up the excellent work! 🚀 Kody Guide: Usage and ConfigurationInteracting with Kody
Current Kody ConfigurationReview OptionsThe following review options are enabled or disabled:
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
There was a problem hiding this comment.
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
| Use: "schooltools", | ||
| Short: "CLI tools for CBE / D2L / Brightspace", | ||
| Version: "0.3.0", | ||
| Version: "0.4.0", |
There was a problem hiding this comment.
🟡 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.
Bumps the version to 0.4.0 and moves the Unreleased changelog section into a dated 0.4.0 entry.
Changes
cmd/root.go:Version0.3.0→0.4.0CHANGELOG.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:
Chores: