Skip to content

Tailwind v4.1.18 migration + core extraction + visual parity gates#3509

Open
alshedivat wants to merge 23 commits intov1.0-devfrom
codex/tailwind-v1-upgrade
Open

Tailwind v4.1.18 migration + core extraction + visual parity gates#3509
alshedivat wants to merge 23 commits intov1.0-devfrom
codex/tailwind-v1-upgrade

Conversation

@alshedivat
Copy link
Owner

@alshedivat alshedivat commented Feb 8, 2026

Summary

  • resolve open review feedback on integration assertions and visual workflow triggers
  • finalize starter wiring for strict v1 ownership boundaries (al_cookie added as plugin-owned cookie runtime)
  • keep starter tests focused on style contract, cross-gem integration, and visual parity
  • add optional Python setup helper for Jupyter deps (bin/setup-python-deps) and update docs (INSTALL.md, CUSTOMIZE.md, FAQ.md, BOUNDARIES.md)

Key wiring changes

  • add al_cookie to Gemfile/plugin list
  • set al_folio.distill.allow_remote_loader: true to match current distill runtime contract
  • update integration checks (integration_distill.sh) to verify pinned distill runtime hash via packaged gem asset

Validation

  • npm run lint:prettier
  • npm run lint:style-contract
  • bash test/integration_bootstrap_compat.sh
  • bash test/integration_distill.sh
  • bash test/integration_upgrade_cli.sh

Copy link

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

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: 2dd34c0d95

ℹ️ 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".

@george-gca george-gca mentioned this pull request Feb 8, 2026
@alshedivat alshedivat changed the title Tailwind-first v1 upgrade path with bootstrap compat + upgrade CLI Tailwind v4.1.18 migration + core extraction + visual parity gates Feb 9, 2026
@alshedivat
Copy link
Owner Author

Addressed the review feedback and follow-up CI issues:

  • Kept tooltips/popovers functional without compat mode via fallback runtime (, ).
  • Removed from compat JS/CSS includes so starter builds no longer fail when compat assets are provided by (, , ).
  • Fixed YAML parsing for date scalars and merged upstream, then reran .

and are now passing on this PR; is still running.

@alshedivat
Copy link
Owner Author

Addressed the review feedback and follow-up CI issues:

  • Kept tooltips/popovers functional without compat mode via the AlFolioUi fallback runtime (assets/js/tooltips-setup.js, assets/js/common.js).
  • Removed bust_file_cache from compat JS/CSS includes so starter builds no longer fail when compat assets are supplied by al_folio_bootstrap_compat (_includes/head.liquid, _includes/scripts.liquid, _includes/distill_scripts.liquid).
  • Fixed al_folio_upgrade YAML parsing for date scalars and merged upstream, then reran upgrade-check.

comments-integration-tests and upgrade-check are passing; visual-regression is still running.

@alshedivat
Copy link
Owner Author

@codex review

Copy link

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

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: 2ee0c61a81

ℹ️ 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".

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