api and token

[christian-rauch]

The action requires setting a api and token but it is not clear from the documentation where to get these values. The example is missing the api input and the link behind "API token" is broken.

The plugin template in Qt Creator creates a workflow with:

- name: Release on Extension Store
  continue-on-error: true
  uses: qt-creator/deploy-qtc-plugin@v0.3
  with:
    api: ${{ secrets.EXTENSION_STORE_API_URL }}
    token: ${{ secrets.EXTENSION_STORE_API_TOKEN }}
    publish: true
    spec: release/${{ env.PLUGIN_NAME }}.json
    download-url-linux-x64: [...]

but there are no examples how to set EXTENSION_STORE_API_URL and EXTENSION_STORE_API_TOKEN.

Some plugins already seem to use this workflow. E.g. the plugin cristianadam.dracula uses the template above and has a passing CI release pipeline, meaning that secrets.EXTENSION_STORE_API_URL and secrets.EXTENSION_STORE_API_TOKEN must have been set to something reasonable.

[Maddimax]

Yes, the key and url was never officially released. In the meantime the mechanism has changed to where its no longer needed. Instead there now is a repository that contains all the plugin metadata here: https://github.com/qt-creator/extension-registry
Be advised though that the Qt Company is still in the process of finializing the leagalese for outside contributions. You can however just create your own fork of the registry for now and register it in Qt Creator (> 17.0).

[christian-rauch]

I see. Does this mean that PRs to https://github.com/qt-creator/extension-registry will also not be considered?

[Maddimax]

They will be considered, and would help us to show interest and urgency to get the mechanism setup ;)