Skip to content

[EC3-2437] Move optimizely-platform to Artifact Registry#1

Merged
EshtiakAlam merged 4 commits into
masterfrom
shihab/EC3-2437-move-to-artifact-reg
Apr 30, 2026
Merged

[EC3-2437] Move optimizely-platform to Artifact Registry#1
EshtiakAlam merged 4 commits into
masterfrom
shihab/EC3-2437-move-to-artifact-reg

Conversation

@EshtiakAlam
Copy link
Copy Markdown
Contributor

Summary

  • Added GitHub Actions workflow to build and publish the optimizely-platform Python package to Google Artifact Registry on version tag pushes (v*.*.*)
  • Replaced hard-coded version in setup.py with setuptools-scm to derive version automatically from git tags

Test plan

  • Verify python -m setuptools_scm resolves version from git tags
  • Verify python -m build produces sdist and wheel with correct version
  • Push a test tag (v0.0.8) and confirm the workflow triggers and publishes to Artifact Registry
  • Confirm existing package consumers are unaffected

- Add GitHub Actions workflow for publishing to Google Artifact Registry
- Update setup.py for SCM versioning
Comment thread .github/workflows/publish.yaml
Copy link
Copy Markdown

@ahmedrafayat ahmedrafayat left a comment

Choose a reason for hiding this comment

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

Missing: Publishing instructions

PR adds publish automation but no docs on how to use it. Please update the README:

Publishing a new version

  1. Ensure all changes are merged to master
  2. Go to Releases → Create a new release on GitHub
  3. Create a new tag (e.g. v0.0.8) targeting master
  4. Add release notes describing changes
  5. Click Publish release
  6. The GitHub Actions workflow will automatically build and publish to Google Artifact Registry

Comment thread .github/workflows/publish.yaml
Comment thread .github/workflows/publish.yaml
Comment thread .github/workflows/publish.yaml
… checks

Co-authored-by: Copilot <copilot@github.com>
Copy link
Copy Markdown

@ahmedrafayat ahmedrafayat left a comment

Choose a reason for hiding this comment

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

All feedbacks were addressed. After merging this PR we will create a new release v0.0.8 (since 0.0.7 tag already exists).

LGTM!

@EshtiakAlam EshtiakAlam merged commit 74dea7e into master Apr 30, 2026
1 check passed
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.

3 participants