Dev.to Security 🔐 Cybersecurity 👁 0 📖 1 min read

glasp (with full clasp compatibility) v0.5.0 – v0.5.3 — Structured Logs, Safer File Sync, and Signed Installs

Summary https://github.com/takihito/glasp 1. glasp v0.5.x — Safer by Default: Symlinks, Path Traversal, and Signed Installs — puts the security angle first, which suits the #security tag. 2. glasp v0.5.0 – v0.5.3 —

Summary

  • https://github.com/takihito/glasp
    • 1. glasp v0.5.x — Safer by Default: Symlinks, Path Traversal, and Signed Installs — puts the security angle first, which suits the #security tag.
    • 2. glasp v0.5.0 – v0.5.3 — slog, config init, and cosign Verification — names the actual features, which suits Go readers.
    • 3. glasp v0.5.x — Hardening a clasp Alternative for Local and CI Use — a theme title rather than a list of changes.

CHANGELOG.md has a version heading that does not match any release tag, plus a duplicated section. While writing the dev.to post covering v0.5.0–v0.5.3, relying on the CHANGELOG alone would have mapped changes to the wrong versions.

Details

  • There is a heading ## [v0.4.1](.../compare/v0.4.0...v0.4.1) - 2026-07-23, but no v0.4.1 tag exists. The release actually published that day is v0.5.0 (slog migration #125, array-form parentId #140, Homebrew #128, etc.). Likely cause: tagpr wrote the CHANGELOG as v0.4.1, then the version was bumped to v0.5.0 without updating the heading.
  • There are two ## [v0.5.2] sections (dated 2026-10-12 and 2026-10-02). The 2026-10-12 one is a superset that includes #192/#193; the 2026-10-02 one appears to be a leftover.
  • v0.5.1 contains only CI/dependency updates, but because there is no v0.5.0 heading, the v0.5.0 → v0.5.1 diff cannot be read from the CHANGELOG.
  • For the article, the correct mapping was confirmed by cross-checking gh release list and git log v0.4.0..v0.5.0.

Proposal

  • Rename the v0.4.1 heading to v0.5.0 (compare v0.4.0...v0.5.0).
  • Remove the duplicate v0.5.2 section dated 2026-10-02.
  • When bumping the version manually after tagpr's [tagpr] prepare for the next release, add a release-checklist step to verify that the CHANGELOG heading was updated too.
  • When writing release notes or articles, cross-check against the tags in gh release list rather than relying on the CHANGELOG alone.
📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.