Repository navigation
Conversation
The repository has no Packagist hook, so Packagist only picks up changes on its weekly crawl: four days after #31 was merged, dev-master on Packagist was still abbe57e. The workflow calls Packagist's update-package API after every push to master and every tag. It needs the PACKAGIST_USERNAME and PACKAGIST_TOKEN secrets of a maintainer of validator/livr on packagist.org, and only warns while they're not set.
koorchik
force-pushed
the
packagist-update
branch
from
October 23, 2026 13:28
2ab9a57 to
c4097e2
Compare
Member
Author
|
Closing in favour of #35: Packagist's own GitHub integration is the standard way to keep the package updated, so a workflow isn't needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs #35
Packagist doesn't pick up changes from this repository: there's no Packagist hook, so it only crawls about once a week. Four days after #31 was merged,
composer require validator/livrstill installeddev-masteratabbe57e, from before the fixes.This adds
.github/workflows/packagist.yml. It calls Packagist'supdate-packageAPI after every push tomasterand every tag, and it can also be started by hand.Setup after merging
A maintainer of
validator/livron packagist.org adds two repository secrets (Settings → Secrets and variables → Actions):PACKAGIST_USERNAME: their Packagist usernamePACKAGIST_TOKEN: their safe API token from https://packagist.org/profile/Until the secrets are set, the workflow only shows a warning and passes. A wrong token fails the job (Packagist answers 403), so the problem shows up.