chore(production): release 0.3.3

[sentient-forms-release]

🤖 I have created a release beep boop

0.3.3 (2026-06-04)

Bug Fixes

• realtime: fetch visitor config without disabling page cache (aa546c0)
• realtime: fetch visitor config without disabling page cache (132d3df)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Greptile Summary

This is an automated release PR generated by Release Please, bumping the plugin version from 0.3.2 to 0.3.3. The only substantive change is a bug fix to the realtime module that fetches visitor config without disabling the page cache.

• .release-please-manifest.json is updated from \"0.3.2\" to \"0.3.3\".
• CHANGELOG.md gains a new 0.3.3 section, but it lists the same bug fix twice under two different commit hashes (aa546c0 and 132d3df), indicating the fix was likely committed or cherry-picked twice onto the source branch.

Confidence Score: 4/5

Safe to merge — only metadata files are touched; no functional code changes are introduced by this PR itself.

The version bump and changelog are straightforward, but the presence of two identical changelog entries backed by distinct commits suggests the underlying bug fix may have been applied twice on the source branch, which is worth verifying before shipping.

CHANGELOG.md — contains duplicate entries that point to two separate commits for the same fix; confirming the source branch history is clean would be prudent.

Important Files Changed

Filename	Overview
.release-please-manifest.json	Version bumped from 0.3.2 to 0.3.3 by Release Please automation.
CHANGELOG.md	New 0.3.3 section added with two changelog entries that describe the same bug fix ("fetch visitor config without disabling page cache"), suggesting a duplicate commit was included.

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant Main as main branch
    participant RP as Release Please Bot
    participant Prod as production branch

    Dev->>Main: commit aa546c0 (realtime: fix visitor config cache)
    Dev->>Main: commit 132d3df (realtime: fix visitor config cache — duplicate)
    RP->>RP: Collect conventional commits since v0.3.2
    RP->>Prod: "Open PR #2 (bump version 0.3.2 → 0.3.3, update CHANGELOG)"
    Note over Prod: Two identical changelog entries<br/>from the two commits

Loading

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
CHANGELOG.md:9-10
**Duplicate changelog entries for the same fix**

The 0.3.3 section lists the same bug fix ("fetch visitor config without disabling page cache") twice, backed by two different commits (`aa546c0` and `132d3df`). 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.

_{Reviews (1): Last reviewed commit: "chore(release): sync WordPress version s..." | Re-trigger Greptile}

[greptile-apps]

Duplicate changelog entries for the same fix

The 0.3.3 section lists the same bug fix ("fetch visitor config without disabling page cache") twice, backed by two different commits (aa546c0 and 132d3df). 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

This is a comment left during a code review.
Path: CHANGELOG.md
Line: 9-10

Comment:
**Duplicate changelog entries for the same fix**

The 0.3.3 section lists the same bug fix ("fetch visitor config without disabling page cache") twice, backed by two different commits (`aa546c0` and `132d3df`). 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.

How can I resolve this? If you propose a fix, please make it concise.