Skip to content

chore: release next - #1428

Merged
toxsick merged 1 commit into
nextfrom
release-please--branches--next
Oct 25, 2026
Merged

toxsick merged 1 commit into
nextfrom
release-please--branches--next

Conversation

@fuf-cavendish

@fuf-cavendish fuf-cavendish commented Dec 19, 2025 •

Copy link
Copy Markdown
Collaborator

🤖 I have created a release beep boop

atelier: 1.0.0-next.1

1.0.0-next.1 (2026-10-25)

⚠ BREAKING CHANGES

  • Remove the pixel-utils heroui export and public Uniform useInput, useUniformField and useUniformFieldArray hook exports. Applications must import pixel-utils/tokens.css, configure Tailwind source scanning and replace custom --heroui-* variables with --pixel-* variables. Custom fields must migrate to the supported controller and form-context APIs. Selectors targeting removed internal markup or state attributes must migrate to the documented slots and supported attributes.

Features

  • replace HeroUI with owned components and Tailwind 4 styling (df27899)

Bug Fixes

  • release: merge main into next and repair prerelease bootstrap (3bb219d)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @fuf-stack/pixel-utils bumped to 2.0.0-next.1
      • @fuf-stack/pixels bumped to 2.0.0-next.1
megapixels: 1.0.0-next.1

1.0.0-next.1 (2026-10-25)

⚠ BREAKING CHANGES

  • Remove the pixel-utils heroui export and public Uniform useInput, useUniformField and useUniformFieldArray hook exports. Applications must import pixel-utils/tokens.css, configure Tailwind source scanning and replace custom --heroui-* variables with --pixel-* variables. Custom fields must migrate to the supported controller and form-context APIs. Selectors targeting removed internal markup or state attributes must migrate to the documented slots and supported attributes.

Features

  • replace HeroUI with owned components and Tailwind 4 styling (df27899)

Bug Fixes

  • release: merge main into next and repair prerelease bootstrap (3bb219d)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @fuf-stack/pixel-motion bumped to 2.0.0-next.1
      • @fuf-stack/pixel-utils bumped to 2.0.0-next.1
      • @fuf-stack/pixels bumped to 2.0.0-next.1
      • @fuf-stack/uniform bumped to 2.0.0-next.1
      • @fuf-stack/veto bumped to 2.0.0-next.1
pixel-motion: 2.0.0-next.1

2.0.0-next.1 (2026-10-25)

Bug Fixes

  • release: merge main into next and repair prerelease bootstrap (3bb219d)
pixel-utils: 2.0.0-next.1

2.0.0-next.1 (2026-10-25)

⚠ BREAKING CHANGES

  • Remove the pixel-utils heroui export and public Uniform useInput, useUniformField and useUniformFieldArray hook exports. Applications must import pixel-utils/tokens.css, configure Tailwind source scanning and replace custom --heroui-* variables with --pixel-* variables. Custom fields must migrate to the supported controller and form-context APIs. Selectors targeting removed internal markup or state attributes must migrate to the documented slots and supported attributes.

Features

  • replace HeroUI with owned components and Tailwind 4 styling (df27899)

Bug Fixes

  • release: merge main into next and repair prerelease bootstrap (3bb219d)
pixels: 2.0.0-next.1

2.0.0-next.1 (2026-10-25)

⚠ BREAKING CHANGES

  • Remove the pixel-utils heroui export and public Uniform useInput, useUniformField and useUniformFieldArray hook exports. Applications must import pixel-utils/tokens.css, configure Tailwind source scanning and replace custom --heroui-* variables with --pixel-* variables. Custom fields must migrate to the supported controller and form-context APIs. Selectors targeting removed internal markup or state attributes must migrate to the documented slots and supported attributes.

Features

  • replace HeroUI with owned components and Tailwind 4 styling (df27899)

Bug Fixes

  • release: merge main into next and repair prerelease bootstrap (3bb219d)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @fuf-stack/pixel-motion bumped to 2.0.0-next.1
      • @fuf-stack/pixel-utils bumped to 2.0.0-next.1
uniform: 2.0.0-next.1

2.0.0-next.1 (2026-10-25)

⚠ BREAKING CHANGES

  • Remove the pixel-utils heroui export and public Uniform useInput, useUniformField and useUniformFieldArray hook exports. Applications must import pixel-utils/tokens.css, configure Tailwind source scanning and replace custom --heroui-* variables with --pixel-* variables. Custom fields must migrate to the supported controller and form-context APIs. Selectors targeting removed internal markup or state attributes must migrate to the documented slots and supported attributes.

Features

  • replace HeroUI with owned components and Tailwind 4 styling (df27899)

Bug Fixes

  • release: merge main into next and repair prerelease bootstrap (3bb219d)

Dependencies

  • The following workspace dependencies were updated
    • dependencies
      • @fuf-stack/pixel-motion bumped to 2.0.0-next.1
      • @fuf-stack/pixel-utils bumped to 2.0.0-next.1
      • @fuf-stack/pixels bumped to 2.0.0-next.1
      • @fuf-stack/veto bumped to 2.0.0-next.1
veto: 2.0.0-next.1

2.0.0-next.1 (2026-10-25)

⚠ BREAKING CHANGES

  • Remove the pixel-utils heroui export and public Uniform useInput, useUniformField and useUniformFieldArray hook exports. Applications must import pixel-utils/tokens.css, configure Tailwind source scanning and replace custom --heroui-* variables with --pixel-* variables. Custom fields must migrate to the supported controller and form-context APIs. Selectors targeting removed internal markup or state attributes must migrate to the documented slots and supported attributes.

Features

  • replace HeroUI with owned components and Tailwind 4 styling (df27899)

Bug Fixes

  • release: merge main into next and repair prerelease bootstrap (3bb219d)

This PR was generated with Release Please. See documentation.

@fuf-cavendish
fuf-cavendish force-pushed the release-please--branches--next branch from 65ce2be to 6ce5d89 Compare December 19, 2025 17:23
@fuf-cavendish
fuf-cavendish force-pushed the release-please--branches--next branch from 6ce5d89 to f3efe7b Compare October 24, 2026 09:33
@coderabbitai

coderabbitai Bot commented Oct 24, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@fuf-cavendish
fuf-cavendish force-pushed the release-please--branches--next branch from f3efe7b to b0e29d8 Compare October 24, 2026 09:38
@fuf-cavendish
fuf-cavendish force-pushed the release-please--branches--next branch from b0e29d8 to c4a9532 Compare October 25, 2026 16:38
@toxsick
toxsick merged commit ec69356 into next Oct 25, 2026
17 checks passed
@fuf-cavendish

Copy link
Copy Markdown
Collaborator Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants