-
Notifications
You must be signed in to change notification settings - Fork 0
chore(production): release 0.3.3 #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,3 +1,3 @@ | ||
| { | ||
| ".": "0.3.2" | ||
| ".": "0.3.3" | ||
| } |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
This file was deleted.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| import{r as e}from"./9lz71eTe.js";const t=!0;export{t}; |
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The 0.3.3 section lists the same bug fix ("fetch visitor config without disabling page cache") twice, backed by two different commits (
aa546c0and132d3df). This typically means the fix was committed twice — either as a cherry-pick or an accidental re-commit — which may leave the production branch with redundant changes. It's worth confirming that both commits are intentional and that the second one doesn't silently overwrite or conflict with the first.Prompt To Fix With AI