Android platform Guide: cordova-android 14 not listed in latest documentation

[GitToTheHub]

Bug Report

Problem

cordova-android 14 is out since 26.03.2025, but the latest Android Platform Guide does not list it. It's only available in the dev docs.

What is expected to happen?

cordova-android 14 should be listed in the lastet docs.

What does actually happen?

It's not listed in the latest docs, only in the dev docs.

Information

Command or Code

Environment, Platform, Device

Version information

Checklist

• I searched for existing GitHub issues
• I updated all Cordova tooling to most recent version
• I included all the necessary information above

[siddhitripathi25]

Hi,I want to work on this issue please assign it to me

[GitToTheHub]

You can make a PR if you want

[siddhitripathi25]

@GitToTheHub Sir I had raised a pr...Please review it

[breautek]

Hi,I want to work on this issue please assign it to me

The docs are more or less tied to the CLI version and 13.0.0 is being voted on for release. So after that is released I'd imagine we will create the doc snapshot.

The dev version of the docs does contain cordova-android 14 details and so it will get included in our next snapshot.

[GitToTheHub]

Should cordova-android 14 not also added to the cordova-cli 12 docs?

[siddhitripathi25]

@GitToTheHub That's a fair question. I added Android 14 to the 12.x docs because:

1. cordova-android 14 has been released and is available for use
2. Users need documentation for the currently available platform version
3. The dev docs already have it - it just wasn't propagated to stable docs
4. Backward compatibility - CLI 12.x can use cordova-android 14.x

If there's a release process where platform docs should only be updated with CLI releases, please let me know the correct approach. I want to make sure this follows the project's documentation practices.

[breautek]

Should cordova-android 14 not also added to the cordova-cli 12 docs?

It really should be.

@GitToTheHub That's a fair question. I added Android 14 to the 12.x docs because:

1. cordova-android 14 has been released  and is available for use

2. Users need documentation for the currently available platform version

3. The dev docs already have it - it just wasn't propagated to stable docs

4. Backward compatibility - CLI 12.x can use cordova-android 14.x

If there's a release process where platform docs should only be updated with CLI releases, please let me know the correct approach. I want to make sure this follows the project's documentation practices.

There's been recent improvements on this process... and as a result it means I'm no longer familiar but I believe there is a gulp or maybe a npm run script that does a "snapshot", which basically makes a - release and copies everything from dev and places it into that version.

https://github.com/apache/cordova-docs/blob/master/doc/working-on-docs.md is the relevant docs on how to build a snapshot/release. I think you can do this in a branch to create a pull request.

There are several ways to build a new release:

npm run update-docs

which sounds like it just updates the latest version. That may be satisfactory but idk if there are any other changes that warrants a timestamp update, which leads to the second path:

npx gulp newversion

which I believe just creates a new 12.x- release which I believe is okay to do in this situation.

I glanced over recent commits and I don't see anything that I think would prevent us creating a new 12.x snapshot.

[GitToTheHub]

@erisu created a PR for this: #1447

[GitToTheHub]

@breautek Thanks for the explanation. Now I understand that all changes in dev have to be synced to 12.x as long as a change don't need some functionality only available in cli 13.x. @erisu started already a talk about improving documentation. I think this will be the right direction as it is very confusing currently.

[erisu]

Closed as resolved. Cordova-Android 14.x is now listed in latest docs.