Skip to content

fix: migrate partytown @builder.io → @qwik.dev@0.14.0#3344

Open
renatomaurovtex wants to merge 6 commits into
devfrom
fix/vte-18-partytown-migration
Open

fix: migrate partytown @builder.io → @qwik.dev@0.14.0#3344
renatomaurovtex wants to merge 6 commits into
devfrom
fix/vte-18-partytown-migration

Conversation

@renatomaurovtex

@renatomaurovtex renatomaurovtex commented May 22, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Replace @builder.io/partytown@^0.6.1 with @qwik.dev/partytown@^0.14.0 in packages/core/package.json
  • Update comment URL in packages/core/lighthouserc.js from BuilderIO/partytown to QwikDev/partytown
  • Re-run pnpm install — lock file updated, old package fully replaced

Test plan

  • @qwik.dev/partytown@0.14.0 resolves in pnpm-lock.yaml
  • @builder.io/partytown no longer present in lock file ✅
  • pnpm install completes without new errors ✅
  • Lint hooks pass ✅

Closes VTE-18

🤖 Generated with Claude Code

Summary by CodeRabbit

  • New Features
    • Added an experimental, opt-in Inter font optimization that self-hosts font assets and reduces render-blocking external requests, including bundling multiple Inter weights.
  • Documentation
    • Documented the new experimental.optimizedFonts option and how it changes bundled font loading behavior.
  • Chores
    • Updated the partytown dependency to the newer package source/version.
  • Tests
    • Added tests to verify expected Inter font weight files and the default value of the new config option.

@renatomaurovtex renatomaurovtex requested a review from a team as a code owner May 22, 2026 17:45
@renatomaurovtex renatomaurovtex requested review from lemagnetic and lucasfp13 and removed request for a team May 22, 2026 17:45
@coderabbitai

coderabbitai Bot commented May 22, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

Migrates the partytown dependency from @builder.io/partytown to @qwik.dev/partytown@^0.14.0 and adds an opt-in experimental.optimizedFonts config flag (default false) that injects @fontsource/inter weight CSS imports into main.scss via a Sass additionalData function in next.config.js. Tests and changelog documentation are included, though the CHANGELOG contains unresolved merge conflict markers.

Changes

Partytown Package Migration

Layer / File(s) Summary
Partytown dependency and comment update
packages/core/package.json, packages/core/lighthouserc.js
@builder.io/partytown is replaced by @qwik.dev/partytown@^0.14.0; the related Lighthouse issue comment URL is updated to the QwikDev org.

experimental.optimizedFonts Opt-in

Layer / File(s) Summary
Config flag, dependency, and changelog
packages/core/discovery.config.default.js, packages/core/package.json, packages/core/CHANGELOG.md
experimental.optimizedFonts is added to the default config (defaults to false); @fontsource/inter is added as a runtime dependency. Note: CHANGELOG.md contains unresolved Git merge conflict markers (<<<<<<< HEAD, =======, >>>>>>>) that must be resolved before merge.
Sass additionalData injection
packages/core/next.config.js, packages/core/src/pages/_app.tsx
next.config.js derives optimizedFontsEnabled from store config, builds appendInterFontsToGlobalStylesheet targeting main.scss, and conditionally applies it to sassOptions.additionalData. _app.tsx gains a comment describing resulting chunk behavior.
Vitest suites for font resolution and config default
packages/core/test/fonts/inter.test.ts, packages/core/test/fonts/optimizedFonts.test.ts
inter.test.ts table-drives require.resolve across all five @fontsource/inter/<weight>.css paths; optimizedFonts.test.ts dynamically imports the config module and asserts optimizedFonts defaults to false.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

  • vtex/faststore#3351: Directly overlaps with the experimental.optimizedFonts self-hosted Inter font feature, touching the same discovery.config.default.js, next.config.js, and _app.tsx surfaces.

Suggested labels

bug

Suggested reviewers

  • lemagnetic
  • lucasfp13
  • emersonlaurentino

Poem

🎨 From Builder's halls to QwikDev's domain,
The partytown package starts anew again.
Inter fonts self-hosted, no Google blocking,
Sass injection keeps the stylesheets unlocking.
optimizedFonts: false — opt in with care,
Your render path stays crisp through the air. 🚀

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: migrating the partytown dependency from @builder.io to @qwik.dev at version 0.14.0, which is the core objective of this PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/vte-18-partytown-migration

Comment @coderabbitai help to get the list of available commands and usage tips.

@codesandbox-ci

codesandbox-ci Bot commented May 22, 2026

Copy link
Copy Markdown

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@pkg-pr-new

pkg-pr-new Bot commented May 22, 2026

Copy link
Copy Markdown

Open in StackBlitz

@faststore/api

npm i https://pkg.pr.new/vtex/faststore/@faststore/api@06c7027

@faststore/cli

npm i https://pkg.pr.new/vtex/faststore/@faststore/cli@06c7027

@faststore/components

npm i https://pkg.pr.new/vtex/faststore/@faststore/components@06c7027

@faststore/core

npm i https://pkg.pr.new/vtex/faststore/@faststore/core@06c7027

@faststore/diagnostics

npm i https://pkg.pr.new/vtex/faststore/@faststore/diagnostics@06c7027

@faststore/lighthouse

npm i https://pkg.pr.new/vtex/faststore/@faststore/lighthouse@06c7027

@faststore/sdk

npm i https://pkg.pr.new/vtex/faststore/@faststore/sdk@06c7027

@faststore/ui

npm i https://pkg.pr.new/vtex/faststore/@faststore/ui@06c7027

commit: 06c7027

@renatomaurovtex renatomaurovtex changed the title fix(deps): migrate partytown @builder.io → @qwik.dev@0.14.0 fix: migrate partytown @builder.io → @qwik.dev@0.14.0 May 26, 2026
renatomaurovtex added a commit that referenced this pull request Jun 1, 2026
…onts (#3351)

## Summary

Adds a new opt-in config flag `experimental.optimizedFonts` (default
`false`). When enabled, FastStore self-hosts the Inter font via
`@fontsource/inter`, eliminating the render-blocking request to
`fonts.googleapis.com` and improving FCP by ~660ms on Lighthouse mobile.

This is the fourth slice of #3345.

> **Stacked PR.** Base branch is `fix/vte-18-partytown-migration`
(#3344), so the `pnpm-lock.yaml` diff here only shows the
`@fontsource/inter` entries instead of the full lockfile reformat that
the partytown PR already includes. After #3344 lands, this PR will be
rebased onto `dev` automatically and the diff against `dev` will remain
minimal.

## How it works

- `discovery.config.default.js` exposes `experimental.optimizedFonts:
false`.
- `packages/core/src/fonts/inter.ts` is an empty stub. When the flag is
`true`, `next.config.js` uses webpack's `NormalModuleReplacementPlugin`
to rewrite imports of `src/fonts/inter` to
`packages/core/fonts/inter.ts` (located **outside** `src/`, so Babel
never scans it).
- `packages/core/fonts/inter.ts` side-effect imports the
`@fontsource/inter` CSS files (400/500/600/700/900), which ship the
self-hosted Inter `.woff2` assets.
- `_app.tsx` imports `src/fonts/inter` because Next.js requires global
CSS imports to live in `_app.tsx`.
- When the flag is `false` (default), webpack never bundles the package
— **zero cost when off**.

## Why plain CSS imports instead of `next/font/google`

The first attempt used `next/font/google`, which fails at build time for
stores shipping a custom `.babelrc.js` (Next.js disables SWC, and
`next/font` requires SWC). `@fontsource/inter` is compiler-agnostic
plain CSS + woff2, so it works with both Babel and SWC.

## Dependency justification (per [AGENTS.md > Dependency
Discipline](https://github.com/vtex/faststore/blob/dev/AGENTS.md#dependency-discipline))

Recorded in detail in `packages/core/CHANGELOG.md`:

- **Need:** powers the opt-in `experimental.optimizedFonts` path;
required by the Babel-safe constraint above.
- **Evaluation:** MIT-licensed, actively maintained (5.x, regular
releases), no critical CVEs, ships its own types/exports.
- **Bundle impact:** zero when the flag is off —
`NormalModuleReplacementPlugin` keeps it out of the module graph.
- **Bucket:** `dependencies` (must be resolvable when stores opt in).
- **Pinning:** declared locally in `packages/core/package.json`,
caret-pinned to `^5.2.6`.

Requesting maintainer approval per the Agent Autonomy Boundaries (new
runtime dependency in a published package).

## How to enable in a store

1. In `discovery.config.js`:

   ```js
   experimental: {
     optimizedFonts: true,
   }
   ```

2. Remove any `<link rel="stylesheet"
href="https://fonts.googleapis.com/...">` from
`customizations/src/fonts/WebFonts.tsx` to avoid duplicate font loads.

If the store uses a font other than Inter, **do not enable this flag** —
keep the existing `WebFonts.tsx` configuration.

## Test plan

- [ ] With `optimizedFonts: false` (default): build is byte-identical to
before, no `.woff2` in the bundle.
- [ ] With `optimizedFonts: true`: `.woff2` files ship, no request to
`fonts.googleapis.com`, Inter renders correctly across weights
400/500/600/700/900.
- [ ] Babel store (custom `.babelrc.js`) builds cleanly with the flag
on.
- [ ] SWC store builds cleanly with the flag on.
- [ ] `pnpm test --filter=@faststore/core` passes (new tests under
`test/fonts/`).
- [ ] Lighthouse mobile FCP improves on a real store with the flag
enabled.


Made with [Cursor](https://cursor.com)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **New Features**
* Added an opt-in experimental `optimizedFonts` flag to self-host the
Inter font (defaults to false), enabling optional local font delivery to
reduce external requests.

* **Documentation**
* Updated changelog with guidance for enabling the font optimization and
related setup notes.

* **Chores**
  * Added runtime dependency to support self-hosted Inter fonts.

* **Tests**
* Added unit tests to verify the default flag value and font-module
behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Cursor <cursoragent@cursor.com>

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
packages/core/discovery.config.default.js (1)

206-221: Note: Production config change requiring review.

This file matches the pattern packages/core/discovery.config*.js specified in the coding guidelines. The new experimental flag defaults to false (opt-in only), which minimizes risk, but careful review is warranted. As per coding guidelines, "Modifying authentication, authorization, CSP, CI/CD pipelines, or production env config requires explicit human approval."

The documentation is comprehensive and the default value ensures backward compatibility.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/core/discovery.config.default.js` around lines 206 - 221, This
change introduces a production-facing config flag optimizedFonts (in
packages/core/discovery.config*.js) and per guidelines requires explicit human
approval; update the PR and the file to signal that: add a clear top-of-file
comment and PR checklist entry stating "Requires explicit production config
approval" and reference the optimizedFonts flag, and ensure the PR includes an
explicit approver (e.g., add a REQUIRED_APPROVAL tag or note in the PR
description and notify the ops/security owner) before merging so the production
config change is reviewed by the appropriate human.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/core/next.config.js`:
- Around line 89-108: When optimizedFonts is enabled we currently add a
webpack.NormalModuleReplacementPlugin but don’t add the equivalent Turbopack
alias, so Turbopack still resolves the empty src/fonts/inter stub; add a
Turbopack resolve alias mapping (turbopack.resolveAlias or
experimental.turbopack.resolveAlias depending on existing config structure) that
maps "src/fonts/inter" to the same path.resolve(__dirname, 'fonts/inter.ts')
used in the webpack plugin so Turbopack will bundle the self-hosted Inter
CSS/woff2; keep this addition guarded by the same
storeConfig.experimental?.optimizedFonts === true check.

---

Nitpick comments:
In `@packages/core/discovery.config.default.js`:
- Around line 206-221: This change introduces a production-facing config flag
optimizedFonts (in packages/core/discovery.config*.js) and per guidelines
requires explicit human approval; update the PR and the file to signal that: add
a clear top-of-file comment and PR checklist entry stating "Requires explicit
production config approval" and reference the optimizedFonts flag, and ensure
the PR includes an explicit approver (e.g., add a REQUIRED_APPROVAL tag or note
in the PR description and notify the ops/security owner) before merging so the
production config change is reviewed by the appropriate human.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 911765bd-55ab-471b-a316-56fa34443b3c

📥 Commits

Reviewing files that changed from the base of the PR and between 0334b85 and d264f27.

⛔ Files ignored due to path filters (2)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml and included by none
  • pnpm-workspace.yaml is excluded by none and included by none
📒 Files selected for processing (9)
  • packages/core/CHANGELOG.md
  • packages/core/discovery.config.default.js
  • packages/core/fonts/inter.ts
  • packages/core/next.config.js
  • packages/core/package.json
  • packages/core/src/fonts/inter.ts
  • packages/core/src/pages/_app.tsx
  • packages/core/test/fonts/inter.test.ts
  • packages/core/test/fonts/optimizedFonts.test.ts
✅ Files skipped from review due to trivial changes (3)
  • packages/core/fonts/inter.ts
  • packages/core/src/fonts/inter.ts
  • packages/core/CHANGELOG.md
🚧 Files skipped from review as they are similar to previous changes (1)
  • packages/core/package.json

Comment thread packages/core/next.config.js Outdated
renatomaurovtex and others added 6 commits June 16, 2026 10:49
Replace @builder.io/partytown@^0.6.1 with @qwik.dev/partytown@^0.14.0
in packages/core/package.json and update the issue comment URL in
lighthouserc.js from BuilderIO/partytown to QwikDev/partytown.

Closes VTE-18

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…onts (#3351)

Adds a new opt-in config flag `experimental.optimizedFonts` (default
`false`). When enabled, FastStore self-hosts the Inter font via
`@fontsource/inter`, eliminating the render-blocking request to
`fonts.googleapis.com` and improving FCP by ~660ms on Lighthouse mobile.

This is the fourth slice of #3345.

> **Stacked PR.** Base branch is `fix/vte-18-partytown-migration`
(#3344), so the `pnpm-lock.yaml` diff here only shows the
`@fontsource/inter` entries instead of the full lockfile reformat that
the partytown PR already includes. After #3344 lands, this PR will be
rebased onto `dev` automatically and the diff against `dev` will remain
minimal.

- `discovery.config.default.js` exposes `experimental.optimizedFonts:
false`.
- `packages/core/src/fonts/inter.ts` is an empty stub. When the flag is
`true`, `next.config.js` uses webpack's `NormalModuleReplacementPlugin`
to rewrite imports of `src/fonts/inter` to
`packages/core/fonts/inter.ts` (located **outside** `src/`, so Babel
never scans it).
- `packages/core/fonts/inter.ts` side-effect imports the
`@fontsource/inter` CSS files (400/500/600/700/900), which ship the
self-hosted Inter `.woff2` assets.
- `_app.tsx` imports `src/fonts/inter` because Next.js requires global
CSS imports to live in `_app.tsx`.
- When the flag is `false` (default), webpack never bundles the package
— **zero cost when off**.

The first attempt used `next/font/google`, which fails at build time for
stores shipping a custom `.babelrc.js` (Next.js disables SWC, and
`next/font` requires SWC). `@fontsource/inter` is compiler-agnostic
plain CSS + woff2, so it works with both Babel and SWC.

Discipline](https://github.com/vtex/faststore/blob/dev/AGENTS.md#dependency-discipline))

Recorded in detail in `packages/core/CHANGELOG.md`:

- **Need:** powers the opt-in `experimental.optimizedFonts` path;
required by the Babel-safe constraint above.
- **Evaluation:** MIT-licensed, actively maintained (5.x, regular
releases), no critical CVEs, ships its own types/exports.
- **Bundle impact:** zero when the flag is off —
`NormalModuleReplacementPlugin` keeps it out of the module graph.
- **Bucket:** `dependencies` (must be resolvable when stores opt in).
- **Pinning:** declared locally in `packages/core/package.json`,
caret-pinned to `^5.2.6`.

Requesting maintainer approval per the Agent Autonomy Boundaries (new
runtime dependency in a published package).

1. In `discovery.config.js`:

   ```js
   experimental: {
     optimizedFonts: true,
   }
   ```

2. Remove any `<link rel="stylesheet"
href="https://fonts.googleapis.com/...">` from
`customizations/src/fonts/WebFonts.tsx` to avoid duplicate font loads.

If the store uses a font other than Inter, **do not enable this flag** —
keep the existing `WebFonts.tsx` configuration.

- [ ] With `optimizedFonts: false` (default): build is byte-identical to
before, no `.woff2` in the bundle.
- [ ] With `optimizedFonts: true`: `.woff2` files ship, no request to
`fonts.googleapis.com`, Inter renders correctly across weights
400/500/600/700/900.
- [ ] Babel store (custom `.babelrc.js`) builds cleanly with the flag
on.
- [ ] SWC store builds cleanly with the flag on.
- [ ] `pnpm test --filter=@faststore/core` passes (new tests under
`test/fonts/`).
- [ ] Lighthouse mobile FCP improves on a real store with the flag
enabled.

Made with [Cursor](https://cursor.com)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

* **New Features**
* Added an opt-in experimental `optimizedFonts` flag to self-host the
Inter font (defaults to false), enabling optional local font delivery to
reduce external requests.

* **Documentation**
* Updated changelog with guidance for enabling the font optimization and
related setup notes.

* **Chores**
  * Added runtime dependency to support self-hosted Inter fonts.

* **Tests**
* Added unit tests to verify the default flag value and font-module
behavior.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
@lemagnetic lemagnetic force-pushed the fix/vte-18-partytown-migration branch from 665d15c to 06c7027 Compare June 16, 2026 13:53
@sonar-workflows

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/core/CHANGELOG.md`:
- Around line 6-88: Resolve the Git merge conflict in the CHANGELOG.md file by
removing the conflict markers (<<<<<<< HEAD, =======, and >>>>>>> 665d15ca7).
Keep the detailed changelog entries from the HEAD branch that document versions
4.3.0-dev.4 through 4.1.2-dev.6, as they provide the complete release history
and should not be deleted. Ensure the final file contains only the changelog
entries without any conflict markers.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 93bcafea-8e0b-4565-b280-468a3128e4a9

📥 Commits

Reviewing files that changed from the base of the PR and between 120580a and 06c7027.

⛔ Files ignored due to path filters (2)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml and included by none
  • pnpm-workspace.yaml is excluded by none and included by none
📒 Files selected for processing (8)
  • packages/core/CHANGELOG.md
  • packages/core/discovery.config.default.js
  • packages/core/lighthouserc.js
  • packages/core/next.config.js
  • packages/core/package.json
  • packages/core/src/pages/_app.tsx
  • packages/core/test/fonts/inter.test.ts
  • packages/core/test/fonts/optimizedFonts.test.ts
✅ Files skipped from review due to trivial changes (3)
  • packages/core/lighthouserc.js
  • packages/core/src/pages/_app.tsx
  • packages/core/test/fonts/inter.test.ts
🚧 Files skipped from review as they are similar to previous changes (2)
  • packages/core/discovery.config.default.js
  • packages/core/next.config.js

Comment on lines 6 to +88
@@ -83,6 +84,8 @@ See [Conventional Commits](https://conventionalcommits.org) for commit guideline

**Note:** Version bump only for package @faststore/core

=======
>>>>>>> 665d15ca7 (chore(core): update CHANGELOG)

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical | ⚡ Quick win

Unresolved merge conflict in CHANGELOG.md must be resolved before merge.

Lines 6–88 contain unresolved Git conflict markers (<<<<<<< HEAD, =======, >>>>>>>). The CHANGELOG cannot be published in this state. Resolve the conflict by selecting which entries to keep, merging them chronologically, or adopting the entries from the winning branch.

🧰 Tools
🪛 markdownlint-cli2 (0.22.1)

[warning] 13-13: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)


[warning] 19-19: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)


[warning] 25-25: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)


[warning] 35-35: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)


[warning] 46-46: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)


[warning] 52-52: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)


[warning] 62-62: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)


[warning] 69-69: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/core/CHANGELOG.md` around lines 6 - 88, Resolve the Git merge
conflict in the CHANGELOG.md file by removing the conflict markers (<<<<<<<
HEAD, =======, and >>>>>>> 665d15ca7). Keep the detailed changelog entries from
the HEAD branch that document versions 4.3.0-dev.4 through 4.1.2-dev.6, as they
provide the complete release history and should not be deleted. Ensure the final
file contains only the changelog entries without any conflict markers.

Source: Linters/SAST tools

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