Skip to content

Feat | LAY-885 cicd publish#7

Merged
m-peko merged 4 commits into
mainfrom
feat/LAY-885-cicd-publish
Feb 27, 2026
Merged

Feat | LAY-885 cicd publish#7
m-peko merged 4 commits into
mainfrom
feat/LAY-885-cicd-publish

Conversation

@Lzok

@Lzok Lzok commented Aug 12, 2025

Copy link
Copy Markdown
Collaborator

No description provided.


env:
TWINE_USERNAME: __token__
TWINE_PASSWORD: ${{ secrets.TWINE_PASSWORD }}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

What is TWINE? Is that something we setup on Pypi?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

name: Publish Python SDK

on:
push:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can we make sure this only runs on the release-branch?

This should never run on main.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

This action runs when a new tag is pushed. The tag must follow this pattern sdk-v*.*.* for this action to run.

Then the publish script makes sure we are working with the release branch

tags:
- "sdk-v*.*.*" # Trigger on version tags like sdk-v0.1.0 etc.

jobs:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can you make sure this job runs on our production github enviornment?

That way it need manual approval before it can run. Like we do in the atlas-app: https://github.com/LayerLens/atlas-app/blob/main/.github/workflows/deploy-production-backend.yaml#L12

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

done

name: Create Release Tag

on:
workflow_dispatch:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Can we make sure this only can be run on the release branch + in the production enviornment so we ensure manual review is needed for publishing?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

done


on:
workflow_dispatch:
inputs:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

How do we specify major vs minor vs patch releases?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

With the current setup we have, I think we should manually bump the version in the _version file, then release the tag.
At least AFAIK that's the approach of braintrust seeing their PRs

@Lzok Lzok force-pushed the feat/LAY-885-cicd-publish branch from 5572988 to ea80fb7 Compare August 22, 2025 15:38
@m-peko m-peko force-pushed the feat/LAY-885-cicd-publish branch from ea80fb7 to 9afc371 Compare February 27, 2026 07:37
@m-peko m-peko merged commit 99a6a15 into main Feb 27, 2026
7 checks passed
@m-peko m-peko deleted the feat/LAY-885-cicd-publish branch February 27, 2026 07:38
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