Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: tailwindlabs/tailwindcss
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v3.4.18
Choose a base ref
...
head repository: tailwindlabs/tailwindcss
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v3.4.19
Choose a head ref
  • 10 commits
  • 11 files changed
  • 2 contributors

Commits on Oct 1, 2025

  1. Don’t tag v3.4 releases as latest

    oops
    thecrypticace committed Oct 1, 2025
    Configuration menu
    Copy the full SHA
    536e38f View commit details
    Browse the repository at this point in the history
  2. Never publish v3 as latest on npm (#19043)

    This PR ensures that if we release v3 in the future, that we don't use
    `latest` as the npm tag, but `v3-lts` instead.
    
    Unfortunately we can't just use `3` or `v3` because they are not valid
    and you will get an error when trying to publish.
    
    Angular uses `v{n}-lts` for the versions they still support:
    https://www.npmjs.com/package/@angular/core?activeTab=versions
    
    Adding a tag is important, because omitting the `--tag` is the same as
    `--tag latest`
    RobinMalfait authored Oct 1, 2025
    Configuration menu
    Copy the full SHA
    7e2dd53 View commit details
    Browse the repository at this point in the history

Commits on Nov 19, 2025

  1. v3: Don’t break sibling-*() functions when used inside calc(…) (#…

    …19335)
    
    The implementation of v3's math operator normalization uses a safe-list
    of function names. Need to add `sibling-index()` and `sibling-count()`
    to this list otherwise when used inside math functions like `calc()`
    they'll get spaces around the `-`.
    thecrypticace authored Nov 19, 2025
    Configuration menu
    Copy the full SHA
    e2b47e8 View commit details
    Browse the repository at this point in the history

Commits on Nov 28, 2025

  1. Fix date

    thecrypticace committed Nov 28, 2025
    Configuration menu
    Copy the full SHA
    82b5c8d View commit details
    Browse the repository at this point in the history

Commits on Dec 9, 2025

  1. Configuration menu
    Copy the full SHA
    90aa4a3 View commit details
    Browse the repository at this point in the history

Commits on Dec 10, 2025

  1. Configuration menu
    Copy the full SHA
    d1fc136 View commit details
    Browse the repository at this point in the history
  2. Bump again

    thecrypticace committed Dec 10, 2025
    Configuration menu
    Copy the full SHA
    9835906 View commit details
    Browse the repository at this point in the history
  3. update workflows

    thecrypticace committed Dec 10, 2025
    Configuration menu
    Copy the full SHA
    c97337a View commit details
    Browse the repository at this point in the history
  4. 3.4.19

    thecrypticace committed Dec 10, 2025
    Configuration menu
    Copy the full SHA
    9eb4e3b View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    f38be22 View commit details
    Browse the repository at this point in the history
Loading