v1.3.9

What's Changed

• chore: release prep for v1.3.9 by @SunDevil311 in #34

Full Changelog: v1.3.8...v1.3.9

v1.3.8

What's Changed

• Feature/outlook surveillance by @SunDevil311 in #33

Full Changelog: v1.3.7...v1.3.8

v1.3.7

What's Changed

• chore: release prep for v1.3.7 by @SunDevil311 in #32

Full Changelog: v1.3.6...v1.3.7

📦 v1.3.6

✍️ Content Updates

• Added new blog post: EFF & SCOTUS ruling (2025-07-01-eff-scotus.md)
• Included promotional assets: eff-scotus-promo.png and .webp

🛠 Dependency Upgrades

• @eslint/js → ^9.30.0
• browserslist → ^4.25.1
• eslint → ^9.30.0
• prettier → 3.6.2

v1.3.5 – Final Registry Fixes for GitHub Packages

This patch ensures reliable authentication and publishing to GitHub Packages by:

• Scoping npm whoami and npm publish directly to https://npm.pkg.github.com/
• Avoiding reliance on implicit registry resolution from .npmrc or package.json

This update finalizes the transition to a fully stable, scoped publish workflow for the blog repository.

v1.3.4 – Legacy Auth Config Cleanup

This release resolves authentication failures caused by a deprecated .npmrc file that incorrectly redirected scoped packages to GitHub Packages. With this file removed, publishing via setup-node and environment-based tokens now works as expected.

🔧 Fixes

• Removed .npmrc with outdated registry and token mappings.
• Re-established clean, token-based authentication flow for scoped packages targeting npmjs.

v1.3.3 – Publish Authentication Fix

This patch finalizes the fix for publishing failures introduced in v1.3.0–v1.3.2 by:

• Re-adding npm ci and upgrading npm to v11.4.1 in publish jobs
• Ensuring Git and environment setup occurs before npm whoami and npm publish
• Adding detailed logging to confirm registry and token configuration

These changes bring the blog workflow in line with the stable, working flow used in the main repo.

v1.3.2 – Fix for Registry Publishing

This patch ensures reliable publishing to both npmjs and GitHub Packages by:

• Upgrading npm to v11.4.1
• Re-adding npm ci in publish jobs
• Validating authentication with npm whoami

These changes address failures introduced in v1.3.0 and v1.3.1 related to lockfile handling and registry auth.

v1.3.1 – Fix for Lockfile Publishing Issue

This patch release corrects a packaging failure introduced in v1.3.0, where the use of cache-dependency-path interfered with registry publishing.

🛠️ Changes

• Removed cache-dependency-path from publish workflows to avoid lockfile-related cache issues.
• Verified presence of package-lock.json in the extracted archive and maintained default npm caching behavior.

v1.3.0 – Git Archive-Based Publishing

🚀 What's New

• Added: A test workflow (publish-test.yml) for validating package structure using dry-run publishing.

🛠️ Changes

• Changed: .github/workflows/publish.yml now uses git archive as the source for published packages, replacing previous methods.
• Reformatted: .github/COMMIT_GUIDE.md to conform to Prettier formatting standards.

⚠️ Breaking

• The switch to git archive may affect workflows or tooling that relied on untracked files in the package output.