Skip to content

Release v0.1.1#8

Merged
avanelsas merged 1 commit intomainfrom
release/v0.1.1
Apr 28, 2026
Merged

Release v0.1.1#8
avanelsas merged 1 commit intomainfrom
release/v0.1.1

Conversation

@avanelsas
Copy link
Copy Markdown
Owner

Summary

Patch release. Bundles the six post-launch fixes that landed on main after v0.1.0:

  • Hosted demo blank-screen fixpublic/index.html, the toolbar brand <picture>, and the CLJS-export plugin's emitted script tag all referenced /<path> (absolute) where <path> (relative) was correct for sub-path hosting on Pages. Fixed across the board.
  • BareDOM 2.4.0 → 2.4.1 (upstream patch release).
  • Vanilla-JS added to the README Features list (it shipped at v0.1.0 but the list was never updated).
  • Plugin-system pointer added so the export-API capability isn't buried.
  • README hero + Why Bareforge? sections — a centered logo at the top + a personal motivation paragraph between the intro and the Features list.

This PR itself bumps package.json 0.0.1 → 0.1.1, syncs package-lock.json, and adds the [0.1.1] entry to CHANGELOG.md with the full breakdown.

Merge plan

Squash-merge → cut v0.1.1 against the resulting commit on main → Pages workflow fires on release: published → demo redeploys with the asset-path fixes and 2.4.1 components.

Test plan

  • All four PR-readiness gates green locally.
  • CI passes the same on this PR.
  • After v0.1.1 release publish, hard-refresh the demo and confirm the editor still loads, the welcome tour fires on a fresh IDB, and the deployed bundle references @2.4.1.

CHANGELOG.md gains a [0.1.1] entry summarising the six post-launch
PRs that fixed the blank Pages demo (asset-path absolutes), bumped
BareDOM 2.4.0 → 2.4.1 (upstream patch), surfaced vanilla-JS in the
README Features list, and added the Why-Bareforge motivation
section.

package.json + package-lock.json version bumped 0.0.1 → 0.1.1
(0.0.1 was the placeholder that never moved to 0.1.0 at launch —
catching up here, since the git tag is the canonical source).

After this lands, cut v0.1.1 against the merged commit and the
Pages workflow auto-fires on `release: published`, redeploying
the demo with the asset-path fixes and 2.4.1 components.
@avanelsas avanelsas merged commit f8573a2 into main Apr 28, 2026
1 check passed
@avanelsas avanelsas deleted the release/v0.1.1 branch April 30, 2026 08:41
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.

1 participant