Skip to content

fix: attach all dist bundles to releases + backfill CHANGELOG - #72

Merged
jackgranatowski merged 2 commits into
mainfrom
fix/release-workflow-and-changelog
May 23, 2026
Merged

fix: attach all dist bundles to releases + backfill CHANGELOG#72
jackgranatowski merged 2 commits into
mainfrom
fix/release-workflow-and-changelog

Conversation

@kiro-agent

@kiro-agent kiro-agent Bot commented May 23, 2026

Copy link
Copy Markdown

This pull request was created by @kiro-agent on behalf of @jackgranatowski 👻

Comment with /kiro fix to address specific feedback or /kiro all to address everything.
Learn about Kiro autonomous agent


Summary

Fixes two issues with the release workflow:

1. Only one CSS file attached to releases

release.yml had files: dist/slashed.essential.css hardcoded. Now attaches all 30 dist files:

  • 5 bundle tiers (essential, optimal, optimal-components, optimal-utilities, full)
  • Each in 3 variants: readable (.css), minified (.min.css), source map (.min.css.map)
  • Both layered and flat versions

2. CHANGELOG empty for recent releases

Releases v0.2.11 and v0.2.12 were created manually via GitHub UI instead of npm run release, so release-it never ran and CHANGELOG was never updated. This PR backfills:

Also bumps package.json version to 0.2.12 to match the published tag.

For future releases

Use npm run release from the command line (not GitHub UI "Create release"). This ensures:

  1. CHANGELOG is generated from conventional commits
  2. Version is bumped in package.json
  3. Tag is created and pushed
  4. The release.yml workflow then picks up the tag, extracts notes from CHANGELOG, and publishes the GitHub Release with all assets attached

Summary by CodeRabbit

  • New Features

    • Added Bricks Builder one-click SLASHED loading integration.
  • Bug Fixes

    • Improved dark-mode contrast and link styling.
  • Documentation

    • Updated README and token documentation.
  • Chores

    • Version bumped to 0.2.12.
    • Enhanced release distribution assets.

Review Change Stack

- release.yml: attach all 30 dist files (readable + minified + source maps
  for all 5 bundle tiers) instead of only slashed.essential.css
- CHANGELOG.md: add missing [0.2.11] and [0.2.12] sections that were skipped
  because releases were created manually via GitHub UI instead of release-it
- package.json: bump version to 0.2.12 to match the published release tag

Co-authored-by: Jack Granatowski <contact@codeslash.net>
@coderabbitai

coderabbitai Bot commented May 23, 2026

Copy link
Copy Markdown

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (11)
  • dist/slashed.essential.css is excluded by !**/dist/**
  • dist/slashed.essential.flat.css is excluded by !**/dist/**
  • dist/slashed.full.css is excluded by !**/dist/**
  • dist/slashed.full.flat.css is excluded by !**/dist/**
  • dist/slashed.optimal-components.css is excluded by !**/dist/**
  • dist/slashed.optimal-components.flat.css is excluded by !**/dist/**
  • dist/slashed.optimal-utilities.css is excluded by !**/dist/**
  • dist/slashed.optimal-utilities.flat.css is excluded by !**/dist/**
  • dist/slashed.optimal.css is excluded by !**/dist/**
  • dist/slashed.optimal.flat.css is excluded by !**/dist/**
  • package-lock.json is excluded by !**/package-lock.json

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c5f00797-b36e-4844-8efc-96fa5a9e174f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
📝 Walkthrough

Walkthrough

This PR prepares the v0.2.12 release by updating the package version to 0.2.12, documenting changelog entries for versions 0.2.11 and 0.2.12 covering Bricks Builder integration and infrastructure updates, and expanding the GitHub Release workflow to distribute additional CSS build artifacts including minified and flat variants with source maps.

Changes

Release Configuration and Documentation

Layer / File(s) Summary
Release notes for v0.2.12 and v0.2.11
CHANGELOG.md
New entries document Bricks Builder one-click loading, removal of audits/ directory, dark-mode contrast and token declaration fixes, documentation corrections, and addition of a CI docs-freshness job.
Package version update to 0.2.12
package.json
Version field incremented from 0.2.10 to 0.2.12 to align with the release tag.
Release workflow asset uploads
.github/workflows/release.yml
Release action configuration expanded from uploading a single CSS file to distributing comprehensive dist/slashed.* variants including minified and flat distributions with source maps for all build targets.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

  • codeslash-dev/SLASHED#60: The expanded release artifact list includes the new dist/slashed.* flat-bundle variants that this PR introduces.
  • codeslash-dev/SLASHED#65: The release workflow updates align with adding back dist/ build outputs so those artifacts exist for distribution.
  • codeslash-dev/SLASHED#51: The changelog documents removal of the audits/ directory, which relates to prior additions in that directory.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'fix: attach all dist bundles to releases + backfill CHANGELOG' directly summarizes both main changes: updating the release workflow to include all distribution files and backfilling missing changelog entries.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/release-workflow-and-changelog

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@package.json`:
- Line 3: package.json version was bumped to "0.2.12" but package-lock.json
still lists "0.2.10" (top-level version and packages[""].version), causing npm
warnings; regenerate the lockfile by running npm install --package-lock-only (or
npm ci then npm install) to update package-lock.json so its top-level version
and packages[""].version match package.json, then commit the updated
package-lock.json.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fcf988c3-38d3-492d-ba56-387e72ce6083

📥 Commits

Reviewing files that changed from the base of the PR and between e44780f and acd4885.

📒 Files selected for processing (3)
  • .github/workflows/release.yml
  • CHANGELOG.md
  • package.json

Comment thread package.json
@jackgranatowski
jackgranatowski merged commit f20370a into main May 23, 2026
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants