Skip to content

feat!: add support for msgspec schemas#844

Merged
abhishekmadan30 merged 1 commit intotaskcluster:mainfrom
abhishekmadan30:schema-support
Feb 5, 2026
Merged

feat!: add support for msgspec schemas#844
abhishekmadan30 merged 1 commit intotaskcluster:mainfrom
abhishekmadan30:schema-support

Conversation

@abhishekmadan30
Copy link
Contributor

No description provided.

@bhearsum
Copy link
Contributor

I see this is failing the free-threading tests; I think that's probably fine - it's not officially supported here yet. AFAICT, free-threading is supported in the unreleased version of msgspec, and they expect to release soon, so we can pick it up when they do.

bhearsum added a commit to bhearsum/taskgraph that referenced this pull request Oct 29, 2025
Over in taskcluster#844, free-threaded python tests are causing `complete-pr` not to run because `msgspec` hasn't released a version that supports it yet. This highlights the fact that free-threading is not officially supported in Taskgraph yet, so we shouldn't block other tasks on these tests.
bhearsum added a commit to bhearsum/taskgraph that referenced this pull request Oct 30, 2025
Over in taskcluster#844, free-threaded python tests are causing `complete-pr` not to run because `msgspec` hasn't released a version that supports it yet. This highlights the fact that free-threading is not officially supported in Taskgraph yet, so we shouldn't block other tasks on these tests.
bhearsum added a commit that referenced this pull request Oct 30, 2025
Over in #844, free-threaded python tests are causing `complete-pr` not to run because `msgspec` hasn't released a version that supports it yet. This highlights the fact that free-threading is not officially supported in Taskgraph yet, so we shouldn't block other tasks on these tests.
Copy link
Collaborator

@ahal ahal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Per https://www.conventionalcommits.org/en/v1.0.0/, please make the prefix feat!: to denote that it's a breaking change. I'd also make the summary shorter, and include the extra context about LegacySchema in a new paragraph.

If you could also update docs/reference/migrations.rst with how to deal with the backwards incompatibility, that would be appreciated! Just make a new 18.x section

@ahal ahal added the BREAKING CHANGE Backwards incompatible request that will require major version bump label Oct 30, 2025
bhearsum added a commit to bhearsum/taskgraph that referenced this pull request Oct 31, 2025
Over in taskcluster#844, free-threaded python tests are causing `complete-pr` not to run because `msgspec` hasn't released a version that supports it yet. This highlights the fact that free-threading is not officially supported in Taskgraph yet, so we shouldn't block other tasks on these tests.
@abhishekmadan30 abhishekmadan30 changed the title feat: added support for msgspec schemas now called Schema along with refactoring volutpous schemas to now be called LegacySchema feat!: added support for msgspec schemas now called Schema along with refactoring volutpous schemas to now be called LegacySchema Nov 3, 2025
@jcristau
Copy link
Contributor

jcristau commented Nov 6, 2025

s/volutpous/voluptuous/ please :)

@abhishekmadan30 abhishekmadan30 changed the title feat!: added support for msgspec schemas now called Schema along with refactoring volutpous schemas to now be called LegacySchema feat!: added support for msgspec schemas now called Schema along with refactoring voluptuous schemas to now be called LegacySchema Nov 6, 2025
@ofek
Copy link

ofek commented Nov 24, 2025

msgspec support for 3.14 has been released https://github.com/jcrist/msgspec/releases/tag/0.20.0

abhishekmadan30 pushed a commit to abhishekmadan30/taskgraph that referenced this pull request Dec 24, 2025
Over in taskcluster#844, free-threaded python tests are causing `complete-pr` not to run because `msgspec` hasn't released a version that supports it yet. This highlights the fact that free-threading is not officially supported in Taskgraph yet, so we shouldn't block other tasks on these tests.
@abhishekmadan30 abhishekmadan30 force-pushed the schema-support branch 3 times, most recently from 4e9cbed to 6659cc7 Compare December 25, 2025 03:42
@abhishekmadan30 abhishekmadan30 force-pushed the schema-support branch 2 times, most recently from 40ece2e to 942de4e Compare February 4, 2026 02:45
Copy link
Collaborator

@ahal ahal left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll stamp one more time. Just double check there weren't any new Schema instances that got added since the last time.

Also a nitpick, the commit summary (first line) is a bit verbose. Consider feat!: add support for msgspec schemas

Then bot the refactoring info in the description part of the commit message.

@abhishekmadan30 abhishekmadan30 changed the title feat!: added support for msgspec schemas now called Schema along with refactoring voluptuous schemas to now be called LegacySchema feat!: add support for msgspec schemas Feb 5, 2026
@abhishekmadan30 abhishekmadan30 merged commit 42b7687 into taskcluster:main Feb 5, 2026
18 checks passed
@abhishekmadan30 abhishekmadan30 deleted the schema-support branch February 6, 2026 00:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

BREAKING CHANGE Backwards incompatible request that will require major version bump

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants