Skip to content

[CD] Upload package to PyPI when creating a release #48

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Mar 26, 2025

Conversation

Vipul-Cariappa
Copy link
Contributor

@vgvassilev, You will first need to follow the instructions at https://docs.pypi.org/trusted-publishers/creating-a-project-through-oidc/ . Make sure the repo/package/workflow names match.

Then merge this PR.
And create a release.

Hopefully, everything goes as expected.


Requesting review from @mvassilev and @henryiii.

@vgvassilev
Copy link
Contributor

@henryiii, can you take a look?

@vgvassilev
Copy link
Contributor

@henryiii ping.

path: dist

- name: Generate artifact attestation for sdist and wheel
uses: actions/[email protected]
Copy link
Contributor

Choose a reason for hiding this comment

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

If you'd like a little less maintenance, you can use v2 instead of v2.2.3. Up to you.

permissions:
id-token: write
attestations: write
contents: read
Copy link
Contributor

Choose a reason for hiding this comment

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

This one's default, you don't need it, though it doesn't hurt.

Copy link
Contributor

Choose a reason for hiding this comment

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

Sorry, I just meant the contents: read line, not the entire block.

Copy link
Contributor

Choose a reason for hiding this comment

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

I guess it's not obvious that I was commenting on a single line, GitHub shows context when you do one line.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fixed it. Could you please have a look at it again.

@vgvassilev vgvassilev merged commit ce22b23 into compiler-research:main Mar 26, 2025
@Vipul-Cariappa Vipul-Cariappa deleted the cd/upload-pypi branch March 26, 2025 09:30
mvassilev pushed a commit that referenced this pull request Mar 29, 2025
* enable running the script without installing as a package

While developing, we can test out changes without pip install

* [CD] Upload package to PyPI when creating a release

* fix according to code review

* fix permissions
vgvassilev pushed a commit that referenced this pull request Apr 10, 2025
* Fix exception occuring in case of illigal stack_frame string.

* Refactor to use pty for capturing output.

* [CD] Upload package to PyPI when creating a release (#48)

* enable running the script without installing as a package

While developing, we can test out changes without pip install

* [CD] Upload package to PyPI when creating a release

* fix according to code review

* fix permissions

* Fix buffer.

* Include stdout and stdin as subwindows.

* Add debugee stdout and stdin windows.

* Intercept gdb output even if it appears with delays.

* Remove " as they may break the json format.

* Fix parsing of the speacial commands to follow the new approach.

* Disable not implemented function call.

* Reduce timeout so that commands are completed quickley.

* Add default values.

* Use full path of the file.

* Use parallel and non blocking calls to speed command execution.

* Fix issuing single commands

* Fix receiving of debuggee output.

* Remove " from the stack, args and locals output.

Prevents from violating the json generated.

* Disable debuginfod.

* Ensure debuggee output is flused before a ywrite.

* Disable stdout flush as it discards debuggee stdout.

* remove additional panels used while developing (#58)

---------

Co-authored-by: Vipul Cariappa <[email protected]>
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.

4 participants