Skip to content

chore: vike@^0.4.252 - #51

Merged
brillout merged 3 commits into
mainfrom
brillout/dev
Jan 12, 2026
Merged

chore: vike@^0.4.252#51
brillout merged 3 commits into
mainfrom
brillout/dev

Conversation

@brillout

Copy link
Copy Markdown
Member

No description provided.

@vercel

vercel Bot commented Jan 12, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
vike-photon-demo Ready Ready Preview, Comment Jan 12, 2026 3:33pm

@brillout

Copy link
Copy Markdown
Member Author

@magne4000 Does it make any difference if I release 0.4.252 or can we use 0.4.251-commit-9c5fb90 and merge this PR as-is?

@magne4000

Copy link
Copy Markdown
Member

It will probably break things with Bati if we use a commit release

@brillout brillout changed the title chore: vike@^0.4.251 chore: vike@^0.4.252 Jan 12, 2026
@brillout
brillout merged commit 018cd19 into main Jan 12, 2026
5 of 6 checks passed
@brillout
brillout deleted the brillout/dev branch January 12, 2026 15:32
@brillout

Copy link
Copy Markdown
Member Author

Fix released in 0.4.252. (Sorry for the self-merging this PR, I just realized I shouldn't have done as it conflicts with the renovate bot's PR.)

@magne4000

Copy link
Copy Markdown
Member

No worries, renovate bot rebase itself, it should be fine 馃憤

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