ci: track upstream instagrapi releases automatically - #434
Merged
Conversation
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.
Summary
instagrapirelease every day at 06:17 UTC, while preserving manual and repository dispatch triggers.X.Y.Zversions against the canonical default-branch baseline, deduplicate exact tracker titles across open and closed issues, and fail closed on malformed or truncated GitHub responses.GITHUB_TOKENwithcontents: readandissues: writepermissions.Security
${{ secrets.GITHUB_TOKEN }}and does not persist checkout credentials.Test Coverage
ghharness verifies exact CLI arguments, version ordering, invalid inputs, API/list/create failures, open and closed deduplication, near-match rejection, saturation fail-closed behavior, and generated issue metadata.Pre-Landing Review
No P0, P1, or P2 findings. Independent task-level spec and quality reviews also passed.
Scope Drift
Scope Check: CLEAN. The public diff contains exactly the intended workflow, tracker script, regression test, and upstream-sync documentation files.
Plan Completion
All implementation and verification tasks are complete. The tracker includes the accepted Bash 3.2 compatibility and fail-closed saturation improvements discovered during review.
Documentation
docs/upstream-sync.mdcovers the maintainer-only tracker as reference, how-to, and explanation; a tutorial is not needed.Documentation Debt
docs/development-guide.md: later mention the daily scheduled check and link to the upstream-sync policy. Deferred to preserve this PR's approved four-file scope.Verification
/bin/bash -n scripts/upstream_sync_tracker.sh676 passed, 3 skipped, 35 subtests passedmkdocs build --strict9440b53