Skip to content

fix: ignore extra runtime assets in hosted update checks#359

Merged
Just-Insane merged 5 commits into
integrationfrom
codex/fix-hosted-update-extra-assets
Jun 25, 2026
Merged

fix: ignore extra runtime assets in hosted update checks#359
Just-Insane merged 5 commits into
integrationfrom
codex/fix-hosted-update-extra-assets

Conversation

@Just-Insane

Copy link
Copy Markdown
Collaborator

Description

Ignore extra runtime-loaded assets when comparing the current page against the hosted app shell. The previous hosted-shell fallback treated any additional lazy-loaded CSS or JS still present in the DOM as proof that a newer shell existed, which could surface a false update banner even when the hosted index.html already matched the current shell assets.

Related to #354
Related to #346

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings

AI disclosure:

  • Partially AI assisted (clarify which code was AI assisted and briefly explain what it does).
  • Fully AI generated (explain what all the generated code does in moderate detail).
    This PR changes the hosted app-shell comparison in appUpdates.ts to parse asset paths into sets and treat the hosted shell as current when all hosted shell assets are already present in the current page, even if extra runtime-loaded assets such as lazy-loaded CSS remain in the DOM. It adds a regression test that models an extra runtime stylesheet and verifies that the update check stays up-to-date instead of surfacing a false positive banner, while preserving the existing service worker and hosted-shell update flows.

@Just-Insane Just-Insane added bug Something isn't working fork-local Charm-specific implementation or deployment concern labels Jun 24, 2026
@Just-Insane Just-Insane enabled auto-merge (squash) June 24, 2026 16:32
@github-actions

github-actions Bot commented Jun 24, 2026

Copy link
Copy Markdown

Sentry Preview Error Triage

No Sentry errors found for this PR's preview deployment as of Thu, 25 Jun 2026 02:11:05 GMT.

This comment updates automatically after each push.

@github-code-quality

github-code-quality Bot commented Jun 24, 2026

Copy link
Copy Markdown

Code Coverage Overview

Languages: JavaScript

JavaScript / code-coverage/vitest

The overall coverage in the branch remains at 27%, unchanged from the branch.

Show a code coverage summary of the most impacted files.
File b5df52e 557323d +/-
src/app/compone...layout/Base.tsx 62% 58% -4%
src/app/utils/appUpdates.ts 93% 93% 0%

Updated June 25, 2026 02:13 UTC
Code Coverage is in Public Preview. Learn more and provide us with your feedback.

Comment thread src/app/utils/appUpdates.ts Outdated

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 96fb924ade

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/app/utils/appUpdates.ts Outdated
Comment thread src/app/utils/appUpdates.ts

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1d311e4ffb

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread src/app/utils/appUpdates.ts Outdated
@sentry

sentry Bot commented Jun 25, 2026

Copy link
Copy Markdown

Sentry Snapshot Testing

Name Added Removed Changed Renamed Unchanged Skipped Status
charm-web-preview
charm-web-preview
- - - - - - ✅ 7 uploaded

Snapshot diffs will appear when we have a base upload to compare against. Make sure to upload snapshots from your main branch.

⚙️ sable Snapshot Settings

@github-actions

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

Status Preview URL Commit Alias Updated (UTC)
✅ Deployment successful! https://pr-359-charm.justin-tech.workers.dev bbabc95 pr-359 Thu, 25 Jun 2026 02:12:46 GMT

@sentry

sentry Bot commented Jun 25, 2026

Copy link
Copy Markdown

Sentry Snapshot Testing

Name Added Removed Changed Renamed Unchanged Skipped Status
charm-web-preview
charm-web-preview
- - - - - - ✅ 7 uploaded

No base snapshots found to compare against. Make sure snapshots are uploaded from your main branch.

⚙️ sable Snapshot Settings

@Just-Insane Just-Insane merged commit d6d8d0b into integration Jun 25, 2026
18 of 19 checks passed
@Just-Insane Just-Insane deleted the codex/fix-hosted-update-extra-assets branch June 25, 2026 02:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working fork-local Charm-specific implementation or deployment concern

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant