Version Packages (integrations/makeswift) - #3191
Merged
jorgemoya merged 2 commits intoAug 28, 2026
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
Unlighthouse Performance Comparison — VercelComparing PR preview deployment Unlighthouse scores vs production Unlighthouse scores. Summary ScoreAggregate score across all categories as reported by Unlighthouse.
Category Scores
Core Web Vitals
|
github-actions
Bot
force-pushed
the
changeset-release/integrations/makeswift
branch
from
August 28, 2026 16:07
18b4af8 to
2d97af5
Compare
Contributor
Author
Bundle Size ReportComparing against baseline from No bundle size changes detected. |
jorgemoya
approved these changes
Aug 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to integrations/makeswift, this PR will be updated.
Releases
@bigcommerce/catalyst-makeswift@1.11.0
Minor Changes
@bigcommerce/catalyst-core@1.11.0release. For more information about what was included in the@bigcommerce/catalyst-core@1.11.0release, see the changelog entry.Patch Changes
#3185
96af6d9Thanks @jordanarldt! - Declare a revalidate window for Makeswift API requests, and addMAKESWIFT_REVALIDATE_TARGETto configure it.The Makeswift SDK tags its responses with
@@makeswiftbut never declares a TTL. Under thefetchCache = 'default-cache'segment config, Next.js reads "no cache config" as "cache forever", so published content was cached indefinitely and only thesite.publishedwebhook could refresh it. On any host Makeswift cannot reach — a local dev server, or a deployment it isn't configured to notify — content froze permanently, and deleting.nextwas the only way to see an edit.Requests for the published site now declare a revalidate window: 3600 seconds by default, or 0 in development, where the webhook never arrives and the TTL is the only invalidation. Draft-mode requests are unchanged; they already opt out of caching, and adding a revalidate value there would trip Next.js's conflicting-config rule and cache the builder's live edits indefinitely.