Skip to content

build: add new workflow for packagist - #1

Merged
adobkin merged 1 commit into
altessa-s:developfrom
melentev-av:feature/add-ci-workflow-for-packegist
May 22, 2026
Merged

build: add new workflow for packagist#1
adobkin merged 1 commit into
altessa-s:developfrom
melentev-av:feature/add-ci-workflow-for-packegist

Conversation

@melentev-av

Copy link
Copy Markdown
Collaborator

Add GitHub Actions workflow .github/workflows/packagist.yml that automatically notifies Packagist when a v* tag is pushed
The workflow sends a POST request to the Packagist API with the repository URL and fails if the response HTTP code is >= 400
Requirements

The following must be configured in the repository or organization settings:

Variable: PACKAGIST_USERNAME — Packagist username
Secret: PACKAGIST_TOKEN — Packagist API token
How to submit the package to Packagist

Go to https://packagist.org/ and log in (or create an account)
Click Submit in the top menu
Enter the repository URL: https://github.com/altessa-s/proto-gen-php
Click Check — Packagist will validate the composer.json
Click Submit to register the package
Go to Profile → API Token and copy your token
In GitHub repo, go to Settings → Secrets and variables → Actions:

  • Add variable PACKAGIST_USERNAME with your Packagist username
  • Add secret PACKAGIST_TOKEN with the copied API token
    From now on, every v* tag push will automatically notify Packagist to update the package metadata
    Test plan

Configure PACKAGIST_USERNAME and PACKAGIST_TOKEN in the repository settings
Submit the package to Packagist (if not already registered)
Push a v* tag and verify the workflow runs successfully
Confirm that Packagist reflects the updated package metadata

@adobkin
adobkin merged commit cf18e36 into altessa-s:develop May 22, 2026
1 check passed
adobkin pushed a commit that referenced this pull request May 22, 2026
Co-authored-by: Andrey Melentev <a.melentev@dagroup.one>
@melentev-av
melentev-av deleted the feature/add-ci-workflow-for-packegist branch May 22, 2026 13:07
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