[renovate-appwrite]

This PR contains the following updates:

Package	Change	Age	Confidence
@angular/animations (source)	21.2.25 → 21.2.26
@angular/common (source)	21.2.25 → 21.2.26
@angular/compiler (source)	21.2.25 → 21.2.26
@angular/compiler-cli (source)	21.2.25 → 21.2.26
@angular/core (source)	21.2.25 → 21.2.26
@angular/forms (source)	21.2.25 → 21.2.26
@angular/platform-browser (source)	21.2.25 → 21.2.26
@angular/platform-browser-dynamic (source)	21.2.25 → 21.2.26
@angular/router (source)	21.2.25 → 21.2.26
@modelcontextprotocol/sdk (source)	1.32.1 → 1.32.2
@tailwindcss/postcss (source)	4.3.3 → 4.3.4
jasmine-core (source)	~5.5.0 → ~5.13.0
postcss (source)	8.5.31 → 8.5.32
tailwindcss (source)	4.3.3 → 4.3.4
tslib (source)	2.8.1 → 2.9.1

---

Release Notes

angular/angular (@​angular/animations)

v21.2.26

Compare Source

upgrade

Commit	Type	Description
bc74d72035	fix	only compile the template contents of a downgraded component

modelcontextprotocol/typescript-sdk (@​modelcontextprotocol/sdk)

v1.32.2

Compare Source

What's Changed

• fix: add explicit | undefined to Transport optional properties (v1.x backport of #​1766) by @​kishormorol in #​2814
• [v1.x] fix: allow registering after connect() when the capability was declared by @​claude[bot] in #​2958
• chore: bump version to 1.32.2 by @​claude[bot] in #​3089

New Contributors

• @​kishormorol made their first contribution in #​2814

Full Changelog: modelcontextprotocol/typescript-sdk@1.32.1...1.32.2

tailwindlabs/tailwindcss (@​tailwindcss/postcss)

v4.3.4

Compare Source

Added

• Add @tailwindcss/turbopack, a Turbopack loader for using Tailwind CSS with Next.js (#​20367)

Fixed

• Ensure watch mode detects changes to symlinked @source files whose real paths aren't otherwise scanned (#​20356)
• Ensure variants using @scope wrap generated utilities instead of nesting inside them (#​20369)
• Ensure nested @scope rules preserve their scoping semantics when flattened (#​20369)
• Preserve declarations directly inside @scope by wrapping them in :where(:scope) (#​20369)
• Ensure generated utilities include a space in empty var() fallbacks (e.g. var(--tw-blur,) → var(--tw-blur, )) (#​20373)
• Canonicalization: convert arbitrary breakpoint and container query variants to named equivalents (e.g. max-[64rem]:flex → max-lg:flex) (#​20380)
• Prevent @tailwindcss/vite from crashing on every edit under Vite's experimental bundledDev mode (#​20379)
• Ensure @tailwindcss/oxide falls back to WASM on platforms without native bindings (@tailwindcss/oxide-wasm32-wasi now installs on all platforms, but only loads when no native binding is available) (#​20383)
• Extract class candidates from Ruby %w and %W literals using angle brackets or custom delimiters (e.g. %w<flex>, %w|flex|), including in Slim and Haml templates (#​20387)
• Preserve whitespace in --default(…) values in functional @utility definitions (e.g. --default(box alphabetic) no longer becomes boxalphabetic) (#​20392)
• Ensure automatic source detection respects negation-based .gitignore files (e.g. /* followed by !/… patterns) (#​20397)
• Ensure root theme('…') namespace lookups in JavaScript plugins and config files return the full namespace object instead of the value of its DEFAULT key (#​20399)
• Skip ignored directories when generating watch globs instead of walking their contents on every rebuild (#​20408)
• Drop invalid UTF-8 candidates during class detection (#​20389)
• Prevent @tailwindcss/vite from forcing full-page reloads for scanned files that Vite does not handle as modules (e.g. .php files) (#​20414)
• Canonicalization: don't merge utilities that reference different theme variables set to CSS-wide keywords like unset (#​20417)
• Don't generate utilities when a modifier is used that would otherwise be silently ignored (e.g. rounded-sm/[5], shadow-sm/foo, stroke-2/50) (#​20419)
• Preserve and, or, and not inside selectors in supports-[…] variants (e.g. supports-[selector(a:not(.foo))]:flex) (#​20420)
• Don't warn about Angular's ::ng-deep and :host-context() when optimizing CSS (#​20434)
• Don't generate CSS for candidates containing an empty additional modifier (e.g. bg-red-500/50/ and group-hover/foo//bar:flex) (#​20466)
• Ensure min-*, max-*, and container query variants with decimal values are sorted numerically (e.g. min-[40.25rem] before min-[40.5rem]) (#​20512)
• Ensure CSS comments ending with \*/ are closed correctly instead of swallowing the CSS that follows (e.g. /* C:\temp\*/) (#​20508)
• Improve style invalidation performance of group-* and peer-* variants (#​20513)
• Ensure cached compilers release their loadModule and loadStylesheet callbacks after compilation (#​20531)
• Canonicalization: preserve & when moving a pseudo-element into * or ** (e.g. [&_::before]:flex → **:[&::before]:flex) (#​20550)
• Ensure the Set.prototype.intersection polyfill in canonicalizeCandidates(…) returns the intersection instead of the first set on Node.js < 22 (#​20562)
• Canonicalization: ensure inline theme(…) alphas with more than 2 decimals migrate to a percentage modifier with the same opacity (e.g. theme(colors.red.500/.12345) → text-red-500/[12.345%], not text-red-500/[12.345]) (#​20563)
• Canonicalization: preserve inline theme(…) alphas as an arbitrary percentage when a custom --opacity-* theme value would change the opacity (e.g. theme(colors.red.500/50%) → text-red-500/[50%] with --opacity-50: 10%) (#​20563)
• Ensure the @property fallback isn't applied in Safari versions that no longer support margin-trim: inline (#​20569)
• Treat viewport units like dvmin and svi and font-relative units like cap and rex as lengths in arbitrary values (e.g. text-[10dvmin] generates font-size instead of color) (#​20516)
• Write plugin logs to stderr in tailwindcss canonicalize so they don't end up in the results on stdout (#​20561)
• Extract class shorthands on later lines when Pug text, comments, or quoted attribute values contain unbalanced brackets, or a quote that doesn't start a string (e.g. input(pattern=/"/.source)) (#​20547, #​20572)
• Underline the correct occurrence of an unsupported data type in --value(…) warnings (#​20554)
• Canonicalization: prefer an existing candidate when collapsing utilities over another utility with the same default theme value (e.g. text-foreground text-primary → text-primary, not text-card-checked-border) (#​20540)
• Canonicalization: don't collapse utilities into a utility that uses another theme variable with the same default value (e.g. mt-card mb-card → my-card, not my-4) (#​20574)
• Ensure @tailwindcss/postcss rewrites relative url(…)s of stylesheets that are inlined before it runs (e.g. @imports in Vite) in optimized builds (#​20576)
• Drop nested rules that put a combinator after a pseudo-element when using pseudo-element variants (e.g. selection:* on a utility with a nested & > * rule) (#​20575)
• Don't generate CSS for arbitrary values with unbalanced parentheses or brackets (e.g. w-[calc(1px] or [--x:a[b]) (#​20577)
• Canonicalization: prevent collapse: true from taking exponentially longer when classes are linked through a utility that sets many properties (e.g. sr-only) (#​20558)
• Ensure & is substituted inside :-moz-any(…) and :-webkit-any(…) in custom variants (e.g. @custom-variant firefox (:-moz-any(&));) (#​20486)
• Ensure the standalone macOS binaries have a valid code signature, so macOS 27 no longer kills them at launch (#​20578)
• Ensure @tailwindcss/turbopack and @tailwindcss/webpack rebuild when the input CSS changes (e.g. next dev with Turbopack no longer serves the CSS of the previous edit) (#​20582)
• Canonicalization: don't drop a utility that sets a --tw-* variable when an unrelated property has the same value (e.g. link mt-4 no longer becomes mt-4 when link sets margin-top: 16px and --tw-translate-x: 16px) (#​20593)
• Decode single-digit hexadecimal escapes in theme variable and @utility names as the CSS spec does (e.g. @theme { --color-\0: red; } no longer registers --color-0) (#​20591)
• Don't treat !important inside strings, comments or url() in declaration values as the important flag (e.g. content: "a !important b") (#​20627)
• Parse a custom property at the end of the input when it has no trailing ; (e.g. --foo: bar as the last declaration) (#​20653)
• Keep a declaration without a ; at the end of the CSS input (e.g. color: red) (#​20655)

jasmine/jasmine (jasmine-core)

v5.13.0

Compare Source

Please see the release notes.

v5.12.1

Compare Source

Please see the release notes.

v5.12.0

Compare Source

Please see the release notes.

v5.11.0

Compare Source

Please see the release notes.

v5.10.0

Compare Source

Please see the release notes.

v5.9.0

Compare Source

Please see the release notes.

v5.8.0

Compare Source

Please see the release notes.

v5.7.1

Compare Source

Please see the release notes.

v5.7.0

Compare Source

Please see the release notes.

v5.6.0

Compare Source

Please see the release notes.

postcss/postcss (postcss)

v8.5.32

Compare Source

• Fixed Input#origin() without opts.from (by @​wleeaf).
• Fixed final-word lookup without source offsets (by @​Don-Yin).
• Fixed explicit start in Warning#toString() (by @​Don-Yin).
• Fixed Promise semantics in LazyResult#finally() (by @​Don-Yin).

Microsoft/tslib (tslib)

v2.9.1: tslib 2.9.1

Compare Source

What's Changed

• Update dependencies by @​jakebailey in microsoft#283
• Switch to new release pipeline by @​jakebailey in microsoft#289
• Port content mapper changes to rewriteRelativeImportExtension by @​andrewbranch in microsoft#295
• Stop requiring an ignored lockfile in release workflows by @​jakebailey in microsoft#296
• Bump tslib to 2.9.0 by @​typescript-automation[bot] in microsoft#297
• Stop running tests in the Azure release pipeline by @​jakebailey in microsoft#298
• Bump tslib to 2.9.1 by @​typescript-automation[bot] in microsoft#299

Full Changelog: microsoft/tslib@v2.8.1...v2.9.1

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Only on Monday (* * * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate CLI.

[renovate-appwrite]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm error code EOVERRIDE
npm error Override for @modelcontextprotocol/sdk@1.32.2 conflicts with direct dependency
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2026-11-11T14_15_23_296Z-debug-0.log

[appwrite]

🟡 Tier B · Needs changes before merging

The changed dependency declaration leaves the committed lockfile out of sync, causing the repository's npm ci CI step to fail.

Updates the declared jasmine-core development dependency from ~5.5.0 to ~5.13.0.

Verdict	New comments	Fixed	Still open
🛑 Changes requested	1	0	0

	Finding	Where
🟠	Update the lockfile with this dependency change	package.json:34

Fix with agent prompt

### Issue 1
package.json:34
**Update the lockfile with this dependency change**

`package-lock.json` still records the root dependency as `~5.5.0` and installs `jasmine-core@5.5.0`, so it no longer matches this declaration. The CI workflow runs `npm ci`, which rejects the out-of-sync lockfile and prevents the build from running; please regenerate and commit the lockfile.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

📂 Walkthrough · 1

File	Change
package.json	Raises the declared jasmine-core version range.

---

_{Reviewed ac152ac · Details · Comment @appwrite review to re-run, or mention @appwrite with a question.}

[appwrite]

🟡 Tier B · 1 blocking finding to address. Summary

[appwrite]

Update the lockfile with this dependency change

package-lock.json still records the root dependency as ~5.5.0 and installs jasmine-core@5.5.0, so it no longer matches this declaration. The CI workflow runs npm ci, which rejects the out-of-sync lockfile and prevents the build from running; please regenerate and commit the lockfile.

Prompt To Fix With AI

This is a comment left during a code review.
Path: package.json
Line: 34

Comment:
**Update the lockfile with this dependency change**

`package-lock.json` still records the root dependency as `~5.5.0` and installs `jasmine-core@5.5.0`, so it no longer matches this declaration. The CI workflow runs `npm ci`, which rejects the out-of-sync lockfile and prevents the build from running; please regenerate and commit the lockfile.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{🟠 Major · bug · Reply if this doesn't apply.}