yamlock 1.1.6

Fixed

• Separated the CLI wordmark from its anchor line so the terminal identity remains readable at a glance.

Install

npm install yamlock@1.1.6

• npm package
• Changelog

Full Changelog: v1.1.5...v1.1.6

yamlock 1.1.5

Changed

• Added breathing room around the CLI identity block so it stays distinct from surrounding terminal output.

Fixed

• Removed an outdated README statement that described the implemented path-pattern selectors as future work.

Install

npm install yamlock@1.1.5

• npm package
• Changelog

Full Changelog: v1.1.4...v1.1.5

yamlock 1.1.4

Changed

• Integrated the canonical wordmark into the README and website chrome, and replaced the legacy CLI banner with the compact terminal identity.

Install

npm install yamlock@1.1.4

• npm package
• Changelog

Full Changelog: v1.1.3...v1.1.4

yamlock 1.1.3

Added

• Brand identity documentation with canonical SVG masters for the yamlock symbol and outlined wordmark, plus reproducible brand-sheet and social-card assets.
• A 1920×1080 browser project and layout regression that keep the wide-screen hero composition within explicit spacing and alignment bounds.

Changed

• Aligned the website favicon and Open Graph image with the canonical brand masters, with content checks that prevent delivery copies from drifting from their sources.
• Pointed npm package homepage metadata to the yamlock project website.
• Made the Playwright preview port configurable so local browser checks can run in isolation from other development servers.

Fixed

• Constrained and centered the desktop hero columns so the copy and interactive scanner remain visually connected on wide displays.

Install

npm install yamlock@1.1.3

• npm package
• Changelog

Full Changelog: v1.1.2...v1.1.3

yamlock 1.1.2

Security

• Require js-yaml 4.3.2 or later within 4.x so empty merge sources count toward the YAML loader's total work limit.
• Limit each YAML merge sequence to 100 source mappings. Regression tests verify the accepted boundary and rejection across encrypt/decrypt/migrate without file writes or source disclosure.

Changed

• Updated the ESLint development dependency to 10.9.1. The Node.js 22+ runtime requirement and encrypted payload formats are unchanged.

Install

npm install yamlock@1.1.2

• npm package
• Changelog

What's Changed

Dependency updates

• chore(deps-dev): bump eslint from 10.9.0 to 10.9.1 in the root-minor-and-patch group by @dependabot[bot] in #4

New Contributors

• @dependabot[bot] made their first contribution in #4

Full Changelog: v1.1.1...v1.1.2

yamlock 1.1.1

Added

• Initial English-only Vue/Vite project website centered on an interactive YAML/JSON encryption scanner, with release-aware content, clear local-processing boundaries, and responsive installation guidance.
• Dedicated website CI and artifact-based GitHub Pages deployment with pinned actions, frozen Yarn installs, stable-release version checks, and minimum permissions.
• GitHub Pages discovery and PWA metadata basics: canonical URLs, social previews, favicon, manifest, robots policy, sitemap, and build-time completeness checks.
• Mobile and desktop Lighthouse budgets plus Playwright browser checks for responsive layout, keyboard controls, reduced motion, local-only behavior, and visual diagnostics.
• Release-gated GitHub Pages deployment that checks out the exact latest stable tag only after package and website quality workflows succeed, with strict release metadata validation and manual recovery for a published tag.

Changed

• Updated the development toolchain for Node.js 22+, added YAML single-document regressions, and limited grouped Dependabot updates to minor/patch releases so future runtime and major upgrades remain independently reviewable.

Fixed

• Corrected the pinned actions/checkout commit used by GitHub Release automation.
• Interactive scanner now starts at the plaintext boundary and reports direction-aware encrypt/decrypt progress during automated and manual movement.
• Improved inactive format controls and footer text contrast to meet automated accessibility checks.

Install

npm install yamlock@1.1.1

• npm package
• Changelog

Full Changelog: v1.1.0...v1.1.1

yamlock 1.1.0

Added

• Tag-gated GitHub Release automation that reuses the full CI matrix, validates the tag against main, derives notes from the matching changelog section, verifies a draft, and publishes the release as latest.
• Structural pathPatterns / --path-patterns selectors for processConfig and CLI encrypt/decrypt/migrate workflows, with whole-segment *, [*], and ** matching, exact-path authentication, and fail-closed validation without reinterpreting existing paths.

Install

npm install yamlock@1.1.0

• npm package
• Changelog

Full Changelog: v1.0.0...v1.1.0

yamlock 1.0.0

yamlock 1.0.0 arrives 8 months and 18 days after the first commit on November 24, 2025.

This release establishes the stable 1.x contract for yamlock's CLI, Node.js API, authenticated payload format, field-path serialization, errors, and TypeScript declarations.

Highlights

• Authenticated payload v2 is now the default, using a fixed AES-256-GCM profile, scrypt key derivation, strict parsing, and authenticated field-path metadata.
• yamlock migrate safely upgrades selected legacy payloads to v2 with dry-run summaries, mixed-format validation, backups, separate outputs, and atomic permission-preserving writes.
• Repeated encryption authenticates and preserves existing payloads by default; strict and explicit force-encryption modes cover automation and intentional nested encryption.
• CLI writes are atomic, reject symbolic-link paths, preserve file modes, detect concurrent source changes, and avoid exposing configuration contents in parse errors.
• The public Node.js API now includes stable error classes and codes, TypeScript declarations, canonical serializePath(segments), and a documented 1.x compatibility policy.
• CI verifies Node.js 22, 24, and 26 on Linux and macOS, coverage thresholds, documentation, release metadata, types, and the installed npm package.

Compatibility and migration

• yamlock requires Node.js 22 or newer and remains an ESM package.
• Existing legacy payloads remain readable throughout the 1.x line. Legacy writing is still available explicitly through yamlock encrypt --legacy or formatVersion: 1, but is deprecated for new data.
• Existing configurations do not need an immediate rewrite. Use yamlock migrate --dry-run first, then migrate with the default backup or a separate output file when ready.
• YAML writes preserve parsed values rather than presentation syntax, so comments, anchors, quoting, tags, and formatting may be normalized. Review the documented YAML rewrite contract before in-place changes.

Install

npm install yamlock@1.0.0

• npm package
• 1.0.0 changelog
• Full changelog: 0.3.0...v1.0.0