'rockcraft init --profile' links to non-existent versioned docs (1.20.0 URLs return 404)

[Rinconjr]

Check existing issues

• I've verified that this bug isn't described by any existing issues.

Bug description

Whenever you run 'rockcraft init --profile' with any extension, either spring-boot-framework, flask-framework, django-framework, fastapi-framework. it redirects to version 1.20.0 of the stable docs.

It seems those are not deployed yet (weird, as it seems that version was released last week).

You get the following:

The docs only work if I downgrade version to '1.19' meaning the url is now like this:

https://documentation.ubuntu.com/rockcraft/1.19/reference/extensions/spring-boot-framework/

it now loads the extension docs successfully.

Or if you simply click here

it will take you to the same url mentioned above.

IMPORTANT

rockcraft.yaml is successfully generated, so this is only an issue docs-wise.

Steps to reproduce

1. Run rockcraft init --profile spring-boot-framework in an empty directory
2. Open the URL printed in the output: https://documentation.ubuntu.com/rockcraft/1.20.0/reference/extensions/spring boot-framework
3. Observe a 404 error page
4. Change the version in the URL to 1.19: https://documentation.ubuntu.com/rockcraft/1.19/reference/extensions/spring-boot-framework/
5. The extension docs load successfully
6. Same behavior with other profiles: flask-framework, django-framework, fastapi-framework

Environment

• Rockcraft version: 1.20.0 (installed via snap, latest/stable)
• OS: Ubuntu 26.04 LTS
• LXD and Multipass both available (not relevant, issue is in CLI output, not build)

rockcraft.yaml

Log output

$ rockcraft init --profile spring-boot-framework
Go to https://documentation.ubuntu.com/rockcraft/1.20.0/reference/extensions/spring-boot-framework to read more about the 'spring-boot-framework' profile.
Successfully initialised project.

$ curl -sI https://documentation.ubuntu.com/rockcraft/1.20.0/reference/extensions/spring-boot-framework | head -1
HTTP/2 404

$ curl -sI https://documentation.ubuntu.com/rockcraft/1.19/reference/extensions/spring-boot-framework/ | head -1
HTTP/2 200

[shAsh-cy]

Investigated this. The init message is built in rockcraft/services/init.py:46-51 from APP_METADATA.versioned_docs_url, which calls craft-application's render_doc_url. In craft-application 7.1.0, the version pinned in uv.lock that function substitutes the version verbatim, so 1.20.0 lands in the URL and 404s. 7.2.0 added major_only=True, which truncates to 1. Confirmed https://documentation.ubuntu.com/rockcraft/1/reference/extensions/spring-boot-framework/ returns 200, and the docs site redirects 1.19, 1.20 and stable there too.

Proposed fix: bump the constraint to craft-application>=7.2.0 and refresh the lock, plus a regression test, the current test in tests/unit/test_cli.py asserts the message against APP_METADATA.versioned_docs_url, the same property that produces it, so it can't catch this.
Happy to open a PR if that's the direction you'd like.

[asanvaq]

Thanks for reporting this! I have added a redirect to the docs, and https://documentation.ubuntu.com/rockcraft/1.20.0/reference/extensions/spring-boot-framework/ now redirects correctly.