chore: bump version to 0.4.2

[mnriem]

Automated version bump to 0.4.2.

This PR was created by the Release Trigger workflow. The git tag v0.4.2 has already been pushed and the release artifacts are being built.

Merge this PR to record the version bump and changelog update on main.

[Copilot]

Pull request overview

Automated release PR to record the 0.4.2 version bump in the package metadata and add the corresponding release notes to the changelog on main.

Changes:

• Bump specify-cli version from 0.4.1 to 0.4.2 in pyproject.toml.
• Add a 0.4.2 section to CHANGELOG.md.

Reviewed changes

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

File	Description
pyproject.toml	Updates project version to 0.4.2.
CHANGELOG.md	Adds release notes for 0.4.2 (currently inserted in a way that disrupts 0.4.1 grouping).

Comments suppressed due to low confidence (1)

CHANGELOG.md:23

• This entry references bumping to 0.4.1, but it is currently listed under the 0.4.2 release notes. It should be removed from 0.4.2 or moved under the 0.4.1 section (as appropriate) to avoid an incorrect changelog.

- chore: bump version to 0.4.1 (#1953)

---

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

[Copilot]

Pull request overview

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

Comments suppressed due to low confidence (2)

.github/workflows/release-trigger.yml:110

• NEW_ENTRY starts with an empty line, and CHANGELOG.md also currently has a blank line immediately after the marker comment. On the next release run, this will insert an extra blank line every time (marker line -> blank from NEW_ENTRY -> existing blank line), slowly bloating the top of the changelog. Consider removing the leading blank line from NEW_ENTRY (or removing the blank line after the marker in CHANGELOG.md) so each insertion produces exactly one separator newline.

            NEW_ENTRY=$(printf '%s\n' \
              "" \
              "## [${{ steps.version.outputs.version }}] - $DATE" \
              "" \
              "### Changed" \
              "" \
              "$COMMITS")

.github/workflows/release-trigger.yml:115

• The changelog update will silently do nothing if the marker comment is missing/changed (awk would just copy the file), but the step still prints "✅ Updated CHANGELOG.md". Please add a guard that verifies the marker exists and that the new version header was inserted (and fail the job if not), so releases can’t proceed with an unmodified changelog.

            awk -v entry="$NEW_ENTRY" '/<!-- insert new changelog below this comment -->/ { print; print entry; next } {print}' CHANGELOG.md > CHANGELOG.md.tmp
            mv CHANGELOG.md.tmp CHANGELOG.md

            echo "✅ Updated CHANGELOG.md with commits since $PREVIOUS_TAG"

---

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