Skip to content

chore(site): re-record the landing page demos - #341

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
refresh-recordings
Open

github-actions[bot] wants to merge 1 commit into
mainfrom
refresh-recordings

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 24, 2026 •

Copy link
Copy Markdown
Contributor

The recordings on the landing page no longer match the engine that
would produce them, or the commits they were taken at.

Re-captured: supabase scrapy lobsters kubernetes deno elasticsearch esphome guzzle phoenix tca trantor obs-backgroundremoval

Any target that failed to record is not in this diff and keeps its
previous recording — still marked stale, so the next run retries it.
The capture step's log names them.

Each recording is a real analysis of the linked commit, so this
diff is the honest answer to "what would Drift say about these
projects today". Worth reading the same way any other claim on that
page is read — particularly anywhere a package moved from a finding
to none, or the other way round.

Opened by .github/workflows/refresh-recordings.yml.

@github-actions
github-actions Bot force-pushed the refresh-recordings branch 3 times, most recently from e4b34cd to 0252117 Compare September 29, 2026 03:54
@github-actions
github-actions Bot force-pushed the refresh-recordings branch from 0252117 to 3db9ed5 Compare October 5, 2026 11:35
@github-actions
github-actions Bot force-pushed the refresh-recordings branch 2 times, most recently from bb1e580 to 29f39fb Compare October 19, 2026 10:00

This branch has not been deployed

No deployments
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.

1 participant