Skip to content

chore(main): release 0.3.0 - #65

Open
frameshift-release-automation[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--frameshift
Open

chore(main): release 0.3.0#65
frameshift-release-automation[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--frameshift

Conversation

@frameshift-release-automation

@frameshift-release-automation frameshift-release-automation Bot commented Nov 1, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

This pull request proposes the next Frameshift release. Merging is a deliberate maintainer action; publication follows the repository's release gate.

0.3.0 (2026-11-01)

Features

  • analyzer: convert async pages with body statements to Astro (#64) (5941c4d)
  • config: add the frameshift.jsonc project configuration (#67) (282e8bd)
  • migrate: add migrate v0 for static App Router sites (#63) (47dfceb)
  • migrate: add plan documents and frameshift plan (#66) (1c336ef)
  • migrate: register transformation rules with versions (#68) (519ce78)
  • migrate: widen conversion and add manifest, replacement, and structural checks (#69) (fb2ef37)

Generated by Release Please. See the release policy.

@frameshift-release-automation
frameshift-release-automation Bot force-pushed the release-please--branches--main--components--frameshift branch 4 times, most recently from e95fdc8 to cca30ba Compare November 1, 2026 20:17
@frameshift-release-automation
frameshift-release-automation Bot force-pushed the release-please--branches--main--components--frameshift branch from cca30ba to f6f519a Compare November 1, 2026 20:37

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

autorelease: pending

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants