-
Notifications
You must be signed in to change notification settings - Fork 77
1.1.1: Add GitHub Actions for publishing Windows dlls on a release #234
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
base: master
Are you sure you want to change the base?
Conversation
Start creating releases again, to have something to attach the artifacts for Windows to
298fabe
to
6640877
Compare
Avoid ambiguity and put `php-` and `ast-` before the corresponding version (e.g. avoid calling it Windows-8.1 for php 8.1). These will be on a release page with artifacts for other platforms
uses: actions/[email protected] | ||
with: | ||
name: ast-${{github.ref_name}}-Windows-php-${{matrix.version}}-${{matrix.arch}}-${{matrix.ts}} | ||
path: .install |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be integrated into the normal workflow, like in apcu?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It can be - largely, I don't want dlls available for non-release versions in case we change our minds about how a feature is implemented before a release - it's a difference of what triggers the build
on:
# https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#release
release:
types: [published]
on: [push, pull_request]
Change the release checklist to start creating releases again.
https://pecl.php.net/package/ast still doesn't have releases, and the php 8.2.0 stable release is close to being published
A similar workflow succeeded in https://github.com/TysonAndre/var_representation/actions/runs/3260935531
This limits dlls to be published on stable releases, to save resources, and to avoid creating dlls for unmerged PRs or functionality that may be revised later.