[zmofei]

Bumps the version to 1.1.0 so mapbox workflow (beta) ships right after 1.0.0. It's a new command, so it's a minor bump under the semver rules from #105.

Stacked on #67. It needs to merge after #67, and #67 after the v1.0.0 tag.

• Cargo.toml and Cargo.lock: 1.1.0.
• CHANGELOG: a ## 1.1.0 - 2026-10-22 heading. Only Add mapbox workflow: install and run multi-step workflows (beta) #67's workflow entry sits under it.
• README: the version-pinned install examples now name 1.1.0.

Tagging and publishing happen in the release pipeline. If this merges on a later day, the heading's date needs updating.

Testing: mapbox --version prints 1.1.0 and tests/changelog.rs passes. The README pins point at a v1.1.0 that won't exist until the release is published.

[mattpodwysocki]

Looks good. Unreleased is left empty, 1.1.0 has only the workflow entry, and with #67 the tree builds, prints mapbox 1.1.0 and passes the full suite. One thing about the order: this targets feat/workflows, so make sure it points at main before merging. GitHub only does that automatically if the branch is deleted when #67 merges.