chore release v1.0.5

[shouze]

• v1.0.5
• v1.0.5

[github-actions]

Coverage after merging chore-release-v1.0.5 into main will be

97.45%

Coverage Report

File	Stmts	Branches	Funcs	Lines	Uncovered Lines
src
aggregate.ts	100%	100%	100%	100%
api.ts	100%	100%	100%	100%
group.ts	100%	100%	100%	100%
output.ts	98.91%	100%	94.74%	99.39%	45
render.ts	97.20%	100%	100%	97.14%	142–145
upgrade.ts	77.01%	100%	88.89%	75.64%	128, 130–132, 79–93
src/render
filter.ts	100%	100%	100%	100%
highlight.ts	99.29%	100%	100%	99.01%	184–185
rows.ts	100%	100%	100%	100%
selection.ts	100%	100%	100%	100%
summary.ts	100%	100%	100%	100%

[Copilot]

Pull request overview

Bumps the project version to v1.0.5 and adjusts the CD workflow artifact rename step to avoid unnecessary/unsafe moves during release builds.

Changes:

• Update package.json version from 1.0.4 to 1.0.5.
• Update CD workflow artifact rename logic to skip mv when the destination artifact file already exists.

Reviewed changes

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

File	Description
package.json	Version bump to 1.0.5 for the release.
.github/workflows/cd.yaml	Changes artifact rename behavior during the build job.

---

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

[Copilot]

The rename guard checks whether the destination file already exists, which can silently skip the move when the dest exists for reasons other than “src and dest are identical” (e.g., a leftover file), potentially uploading a stale artifact. Consider instead checking whether the computed src path equals the destination path and only skipping mv in that case; otherwise keep overwriting (mv -f) to ensure the artifact always matches the current build output.

Suggested change

	[ -f "dist/${{ matrix.artifact }}" ] || mv -v "$src" "dist/${{ matrix.artifact }}"
	dest="dist/${{ matrix.artifact }}"
	if [ "$src" != "$dest" ]; then
	mv -fv "$src" "$dest"
	fi