Bump the uv-lockfile group with 4 updates

[dependabot]

Updates the requirements on tiled[client], pyside6, tiled[client,server] and setuptools-scm[toml] to permit the latest version.
Updates tiled[client] to 0.2.14

Release notes

Sourced from tiled[client]'s releases.

v0.2.14

What's Changed

• Adding a check for authentication links in Context.whoami and a message if they are not present by @​sjulian4 in bluesky/tiled#1418
• Ensuring that requesting to update the metadata with values that do not serialize as a JSON object raises an exception in the client by @​sjulian4 in bluesky/tiled#1408
• Strengthen back-compatibility by @​genematx in bluesky/tiled#1424

Full Changelog: bluesky/tiled@v0.2.13...v0.2.14

Changelog

Sourced from tiled[client]'s changelog.

Changelog

Unreleased

Fixed

• Skip the array-ref streaming-cache update in put_data_source when the data source is not an array.
• Strengthen the server-side backcompatibility. Strip the newly added Asset.size field from metadata responses when the request comes from a python-tiled client older than v0.2.13, whose Asset dataclass has no size field and would otherwise crash in DataSource.from_json with an unexpected keyword argument.
• Widen assets.size from INTEGER (int32) to BIGINT (int64) so the server can register single files larger than ~2.1 GB without an int32 out of range error from PostgreSQL. Includes an alembic migration; SQLite is unaffected (its INTEGER affinity already stores 64-bit values).

v0.2.13 (2026-07-08)

Fixed

• Expand the functionality of HDF5Adapter to handle object-dtyped data: variable-length strings are coerced to fixed-length bytes, non-string object dtypes (e.g. vlen arrays) fall back to an empty placeholder that preserves the original shape.
• The metadata revisions endpoint now reports the total revision count, so all revisions can be paged through via the API.
• Surface Asset.size (the byte length of each underlying file) on the Asset API model. tiled register populates it via os.stat() for non-directory file:// assets walked from the local filesystem. For assets in object storage, callers can compute size via the new tiled.storage.size_from_uri helper, which dispatches to os.stat() for file:// URIs and obstore.head() for s3:///az:///gs://. The corresponding ORM column has existed since the catalog schema was created but was previously never written or read.
• New bytes structure family for cataloging opaque byte payloads that lack a useful logical structure (PDFs, firmware blobs, proprietary binary formats, etc.).
• BaseClient.raw_export() accepts a MutableMapping (e.g. a dict) as its destination, streaming each asset into an in-memory io.BytesIO keyed by the on-disk-equivalent layout (<filename> for a single asset; <asset_id>/<filename> for multi-asset nodes). No filesystem I/O is performed in this mode.

Fixed

... (truncated)

Commits

• 995fa00 Merge pull request #1424 from genematx/fix-asset-size
• 462d79c BUG: handle list-shaped response data in _model_dump_backcompat
• 9a71f62 MNT: Changelog
• 8bf74b9 BUG: strip Asset.size from responses to pre-0.2.13 python-tiled clients
• 6a28354 MNT: consolidate python-tiled User-Agent parsing into _backcompat helper
• 3c7f913 Ensuring that requesting to update the metadata with values that do not seria...
• 10b6f9c Adding a check for authentication links in Context.whoami and a message if th...
• 541272c Merge pull request #1409 from gnzng/fix-1389-revisions-pagination
• 2c5a838 TST: empty revisions
• da627b2 ENH: use the same DB session for revisions and count
• Additional commits viewable in compare view

Updates pyside6 from 6.9.3 to 6.11.1

Updates tiled[client,server] to 0.2.14

Release notes

Sourced from tiled[client,server]'s releases.

v0.2.14

What's Changed

• Adding a check for authentication links in Context.whoami and a message if they are not present by @​sjulian4 in bluesky/tiled#1418
• Ensuring that requesting to update the metadata with values that do not serialize as a JSON object raises an exception in the client by @​sjulian4 in bluesky/tiled#1408
• Strengthen back-compatibility by @​genematx in bluesky/tiled#1424

Full Changelog: bluesky/tiled@v0.2.13...v0.2.14

Changelog

Sourced from tiled[client,server]'s changelog.

Changelog

Unreleased

Fixed

• Skip the array-ref streaming-cache update in put_data_source when the data source is not an array.
• Strengthen the server-side backcompatibility. Strip the newly added Asset.size field from metadata responses when the request comes from a python-tiled client older than v0.2.13, whose Asset dataclass has no size field and would otherwise crash in DataSource.from_json with an unexpected keyword argument.
• Widen assets.size from INTEGER (int32) to BIGINT (int64) so the server can register single files larger than ~2.1 GB without an int32 out of range error from PostgreSQL. Includes an alembic migration; SQLite is unaffected (its INTEGER affinity already stores 64-bit values).

v0.2.13 (2026-07-08)

Fixed

• Expand the functionality of HDF5Adapter to handle object-dtyped data: variable-length strings are coerced to fixed-length bytes, non-string object dtypes (e.g. vlen arrays) fall back to an empty placeholder that preserves the original shape.
• The metadata revisions endpoint now reports the total revision count, so all revisions can be paged through via the API.
• Surface Asset.size (the byte length of each underlying file) on the Asset API model. tiled register populates it via os.stat() for non-directory file:// assets walked from the local filesystem. For assets in object storage, callers can compute size via the new tiled.storage.size_from_uri helper, which dispatches to os.stat() for file:// URIs and obstore.head() for s3:///az:///gs://. The corresponding ORM column has existed since the catalog schema was created but was previously never written or read.
• New bytes structure family for cataloging opaque byte payloads that lack a useful logical structure (PDFs, firmware blobs, proprietary binary formats, etc.).
• BaseClient.raw_export() accepts a MutableMapping (e.g. a dict) as its destination, streaming each asset into an in-memory io.BytesIO keyed by the on-disk-equivalent layout (<filename> for a single asset; <asset_id>/<filename> for multi-asset nodes). No filesystem I/O is performed in this mode.

Fixed

... (truncated)

Commits

• 995fa00 Merge pull request #1424 from genematx/fix-asset-size
• 462d79c BUG: handle list-shaped response data in _model_dump_backcompat
• 9a71f62 MNT: Changelog
• 8bf74b9 BUG: strip Asset.size from responses to pre-0.2.13 python-tiled clients
• 6a28354 MNT: consolidate python-tiled User-Agent parsing into _backcompat helper
• 3c7f913 Ensuring that requesting to update the metadata with values that do not seria...
• 10b6f9c Adding a check for authentication links in Context.whoami and a message if th...
• 541272c Merge pull request #1409 from gnzng/fix-1389-revisions-pagination
• 2c5a838 TST: empty revisions
• da627b2 ENH: use the same DB session for revisions and count
• Additional commits viewable in compare view

Updates setuptools-scm[toml] to 10.2.0

Release notes

Sourced from setuptools-scm[toml]'s releases.

setuptools-scm v10.2.0

Added

• Restore Python 3.8 and 3.9 support, re-enabling use as a build dependency for projects like scikit-build that still support these versions. (#1445)

Miscellaneous

• Move PKG-INFO discovery tests from vcs-versioning to setuptools-scm where the entry points are registered. (#1446)

Commits

• a705891 Merge pull request #1448 from pypa/release/main
• 630448e Prepare release: setuptools-scm v10.2.0, vcs-versioning v2.2.0
• aaf4950 Merge pull request #1445 from RonnyPfannschmidt/python-legacy
• dd60bf9 Merge pull request #1447 from RonnyPfannschmidt/fix/1446-move-pkginfo-tests
• 535f5ff fix: move PKG-INFO discovery tests to setuptools-scm (#1446)
• 3546a0e feat: restore Python 3.8 and 3.9 support
• 0cde123 Merge pull request #1443 from pypa/release/main
• 51bc391 Prepare release: vcs-versioning v2.1.2
• 310f3c3 Merge pull request #1442 from RonnyPfannschmidt/fix/1439-metadata-workdir-cus...
• b7b70a8 fix: don't re-parse stored tags through tag_regex in MetadataWorkdir (#1439)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions