Release 1.10.0 #7283

Checklist

• I've read the contribution guidelines.
• I've searched other issues and no duplicate issues were found.
• I've agreed with the maintainers that I can plan this task.

Description

We tagged the last release, 1.9.0, on 2026-07-16 (#7140). Since then, main moved to a new structure, but the release pins did not. The two now disagree, and users can get a broken combination.

The published Docker images build from the pinned repositories/autoware.repos file (vcs import in the build workflow). The pins are autoware_universe 0.52.1 and autoware_launch 0.52.0. Launch files from these versions read flat model file names, for example lidar_centerpoint/centerpoint_tiny_ml_package.param.yaml.

The artifacts ansible role on main downloads the new Hugging Face layout. This layout uses variant subdirectories, for example lidar_centerpoint/tiny/ml_package.param.yaml. The launch files on main select the variant subdirectory.

When a user runs a published image with model files from main, e2e_simulator.launch.xml crashes because the flat file does not exist. We found this while we tested the CARLA demo (#7264) with the published universe-cuda-jazzy image.

The artifacts role README tells users with pinned repos to download model files from the latest release tag. This mitigation works, but it is easy to miss.

The release also unblocks the CARLA demo on the Kashiwanoha map. The map is published as the dataset AutowareFoundation/map-carla-kashiwanoha. CARLA has no level for this area, so the bridge must accept a world built from OpenDRIVE. That support is the autoware_carla_interface work on main after 0.52.1: the carla_map override, ground snap, the standstill throttle, and the world load fixes. None of it is in a published image today. The launch side landed on 2026-09-03.

• feat(autoware_launch): make the dummy vehicle and dummy perception to… autoware_launch#1966

A new release closes the gap. After the release, the images, the launch files, and the model files agree on one layout. The release cadence also supports this: 1.8.0 on 2026-05-04, 1.9.0 on 2026-07-16, and the next quarterly window is near.

Purpose

Publish a release in which the pinned repositories, the published Docker images, and the model files from the artifacts role are consistent.

Possible approaches

Follow the same process as the 1.9.0 release (#7140):

1. Release each repository. Each release has a version bump PR on main, a release branch PR, and a GitHub release.
2. Update repositories/autoware.repos with the new versions.
3. Test the demos with the new pins.
4. Release the changed packages on the ROS buildfarm.
5. Update the release documentation with the new stable version.

The workflow improvements from #7083 can make these steps simpler.

We audited all 31 entries of repositories/autoware.repos on 2026-08-21. The commit counts for autoware_universe, autoware_launch and autoware_core were refreshed on 2026-09-03. We compared each pin against the upstream tags and branches. The table at the end of this issue shows the result for every entry. The checklists below follow from that audit.

Definition of done

New releases (the repository has commits after its latest tag):

• Release autoware_universe 0.53.0 (302 commits after 0.52.1, includes the breaking centerpoint model-manifest refactor: refactor(autoware_lidar_centerpoint)!: consume per-variant model folders via a model manifest autoware_universe#13087, refactor(autoware_lidar_centerpoint)!: scope model params to the manifest and check its version autoware_universe#13211) chore: update build_depends_stable.repos autoware_universe#13448 chore: update package.xml and CHANGELOG.rst for 0.53.0 autoware_universe#13447
• Release autoware_launch 0.53.0 (46 commits after 0.52.0, includes the breaking launcher restructure: refactor(tier4_perception_launch)!: select centerpoint variant folder in the launcher autoware_launch#1930, refactor(perception)!: modularize perception launchers into reusable feature units autoware_launch#1942)
• Release autoware_core 1.10.0 (166 commits after 1.9.0) chore: update humble to 1.10.0 autoware_core#1477
• Release autoware_internal_msgs 1.16.0 (1 commit after 1.15.0). Released 2026-09-04, tracking issue: Release version 1.16.0 autoware_internal_msgs#96
• Release autoware_lanelet2_extension 1.3.0 ([2 commits after 1.2.0] (autowarefoundation/autoware_lanelet2_extension@1.2.0...main)) chore: bump version (1.3.0) and update changelog autoware_lanelet2_extension#117
• Release autoware_simple_planning_simulator 1.1.0 (5 commits after 1.0.0) chore: bump version (1.1.0) and update changelog autoware_simple_planning_simulator#20
• Release ros2_socketcan 1.4.0 (9 commits after 1.3.0). The pin then moves from a commit hash to the new tag.
• Release bevdet_vendor 0.1.1 (1 fix commit after 0.1.0)
• Release managed_transform_buffer 0.2.1 (2 chore commits after 0.2.0) https://github.com/autowarefoundation/managed_transform_buffer/releases/tag/0.3.0

Landed on main for the CARLA Kashiwanoha demo, so it ships with the release:

• feat(autoware_launch): make the dummy vehicle and dummy perception to… autoware_launch#1966 (merged 2026-09-03)

Optional for the release, only if reviewed in time. The release does not wait for them:

• feat(autoware_carla_interface): publish CARLA vehicles as ground truth detections autoware_universe#13321 (ground truth detections from CARLA)
• feat(autoware_carla_interface): add a tick follower mode for co-simul… autoware_universe#13286 (tick follower mode)

Pin updates to versions that already exist (no new release necessary):

• Update the autoware_utils pin from 1.9.0 to 1.10.0
• Update the nebula pin from v1.1.0 to v1.2.0 chore: update nebula version to v1.2.0 #7332
• Update the sync_tooling_msgs pin from v0.2.10 to v0.2.11 chore: update sync_tooling_msgs to v0.2.11 #7334
• Update the llh_converter pin to the ros2 branch head (one fix commit after the current pin)
• Optional: update the transport_drivers pin to the main head (one CI-only commit)

Coordination with TIER IV:

• Ask TIER IV to tag a new agnocast version (105 commits after 2.3.5), then update the pin chore: update agnocast to 2.4.1 #7327
• Ask TIER IV to tag a final tier4_autoware_msgs v0.70.0 (the current pin is the RC tag v0.70.0-rc), then update the pin chore: update tier4_autoware_msgs to 1.0.0-alpha #7331

Meta-repository:

• Update repositories/autoware.repos with all new versions
• Test the demos with the new pins
• On the ROS buildfarm, release the changed packages: autoware_core, autoware_internal_msgs, autoware_lanelet2_extension, and autoware_utils 1.10.0 if it is not on the buildfarm yet
• Update the release documentation

Audit of all pinned repositories

cc @mitsudome-r