Skip to content
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

feat: add workflows for publishing single package #1070

Merged
merged 3 commits into from
Apr 4, 2024

Conversation

joaoandre-avaiga
Copy link
Collaborator

No description provided.

Copy link
Contributor

github-actions bot commented Apr 2, 2024

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines Covered Coverage Threshold Status
17903 15722 88% 0% 🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: 4f6abb7 by action🐍

Copy link
Member

@jrobinAV jrobinAV left a comment

Choose a reason for hiding this comment

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

Must be tested on dev version soon.

@@ -0,0 +1,247 @@
name: Build all taipy packages and release them
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
name: Build all taipy packages and release them
name: Build and release one taipy sub-package

description: "The version of the package to be released"
required: true
target_package:
description: "The package to be released"
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
description: "The package to be released"
description: "The package to be released (gui, config, core, rest, templates, taipy)"

description: "The tag of the package to publish on Pypi (ex: 1.0.0, 1.0.0.dev0)"
required: true
target_package:
description: "The package to be released"
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
description: "The package to be released"
description: "The package to be released (gui, config, core, rest, templates, taipy)"

jrobinAV
jrobinAV previously approved these changes Apr 3, 2024
@joaoandre-avaiga joaoandre-avaiga force-pushed the feature/publish-single-package branch from b40c0e6 to c01ffa2 Compare April 4, 2024 00:18
@joaoandre-avaiga joaoandre-avaiga force-pushed the feature/publish-single-package branch 4 times, most recently from f23b319 to 0540287 Compare April 4, 2024 00:30
@joaoandre-avaiga joaoandre-avaiga force-pushed the feature/publish-single-package branch from 4f6abb7 to be6600c Compare April 4, 2024 00:35
@joaoandre-avaiga
Copy link
Collaborator Author

Im merging this because otherwise I can't trigger the action without it being on develop

@joaoandre-avaiga joaoandre-avaiga merged commit 260b420 into develop Apr 4, 2024
15 checks passed
@joaoandre-avaiga joaoandre-avaiga deleted the feature/publish-single-package branch April 4, 2024 00:36
HarryRegel added a commit to HarryRegel/taipy that referenced this pull request Apr 5, 2024
feat: add workflows for publishing single package (Avaiga#1070)
joaoandre-avaiga added a commit that referenced this pull request Apr 8, 2024
* feat: add workflows for publishing single package

* feat: remove unneeded taipy package job
joaoandre-avaiga added a commit that referenced this pull request Apr 8, 2024
* feat: add workflows for publishing single package (#1070)

* feat: add workflows for publishing single package

* feat: remove unneeded taipy package job

* fix: whitespace in variable name (#1101)

* feat: add version interval to taipy dependencies
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