Skip to content

Conversation

@joshyam-k
Copy link

@joshyam-k joshyam-k commented Nov 14, 2025

DRAFT

note: claude wrote the initial version of tests for extension-list, but I went back in and did a ton of editing and removing.

TODO:

  • add de-duplication logic to make sure we never keep an extension in the prerelease list after we bump it to release.
  • add prerelease extension list to GalleryFeed config on Connect development.gcfg for further testing

- name: Get manifest extension version
run: |
MANIFEST_VERSION=$(semver -c $(jq -c -r '.extension.version' < ./extensions/${{ inputs.extension-name }}/manifest.json))
MANIFEST_VERSION=$(semver -c -p $(jq -c -r '.extension.version' < ./extensions/${{ inputs.extension-name }}/manifest.json))
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the -p flag makes it so we always include prerelease versions in range matching.

uses: actions/upload-artifact@v4
with:
name: release-${{ inputs.extension-name }}.json
name: release-${{ inputs.extension-name }}${{ env.PRERELEASE == 'true' && '-prerelease' || '' }}.json
Copy link
Author

@joshyam-k joshyam-k Nov 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

artifact gets a '-prerelease' suffix to make for easier management in extensions.yml


# don't add prerelease files to extensions.json on main
# TODO: verify this does what we want
- name: Remove prerelease files
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to make sure we don't fetch pre-release versions here.

if: ${{ always() && needs.fetch-prerelease-releases.result == 'success' && needs.fetch-prerelease-releases.outputs.releases != '[]' }}
env:
RELEASES: ${{ needs.fetch-prerelease-releases.outputs.releases }}
EXTENSION_LIST_FILE: extensions-prerelease.json
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

writing to a separate file called extensions-prerelease.json

@joshyam-k
Copy link
Author

@dotNomad zero rush on this, but if you want to take an early look at this to make sure I'm not driving things in the complete wrong direction that would be helpful! Still a couple pieces to do, but most of the basic structure is there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants