This repository was archived by the owner on Jul 29, 2026. It is now read-only.
chore: prepare repository for archiving - #497
Merged
Merged
Conversation
Bring `main` in line with the archive plan so the repo goes quiet before it is marked read-only on GitHub. - Sync the README with the one shipped in the 0.19.0.post1 final release, so the GitHub landing page and the PyPI page tell the same story. - Remove dependabot.yml. Daily github-actions updates with a one-day cooldown produced roughly twenty of the commits since v0.19.0 and would keep opening PRs against a repo nobody is maintaining. - Remove the nightly cron from tests.yml, along with the now-unreachable "Nightly - run unit tests with Haystack main branch" step and the `event_name == 'schedule'` arm of the AWS auth condition. - Remove project.yml, which added new issues to a triage board. Archiving disables Actions anyway, but doing this first means no failing nightly runs or stray dependabot PRs in the window before that happens. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
`docusaurus_sync.yml` regenerates the API reference and opens a PR into deepset-ai/haystack writing `docs-website/reference/experiments-api/**`. In that repo, `auto_approve_api_ref_sync.yml` auto-approves and squash- merges any HaystackBot `sync-docusaurus-api-reference` PR touching those paths, so the sync lands without human review. Its tag trigger is spent — 0.19.0.post1 was the final release, and that tag was cut from a branch where this workflow was already deleted, so no sync PR fired. What remains is the `workflow_dispatch` trigger, and the workflow's own warning now applies permanently: this repository has evolved significantly since the last release (Agent, HITL, breakpoints and mem0 were all deleted from `main` without being released). A manual run would generate a reduced API reference and auto-merge it into Haystack, recreating the very directory deepset-ai/haystack#12177 removes. Removing it is the only way to close that path, since a workflow with `workflow_dispatch` stays runnable by anyone with write access for as long as Actions are enabled. Keeping `pypi_release.yml`: it has no manual trigger, fires only on a `v*` tag, and documents how the final release was produced. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Related Issues
0.19.0.post1, is published on PyPI.Proposed Changes:
0.19.0.post1dependabot.yml. Daily github-actions updates produced ~20 of the commits sincev0.19.0and would keep opening PRs against an unmaintained repo.tests.yml, plus the now-unreachable nightly step and theevent_name == 'schedule'arm of the AWS auth condition.project.yml(issue triage board automation).docusaurus_sync.ymlHow did you test it?
Notes for the reviewer
I'll need to manually revoke CI secrets, remove the PyPI trusted-publisher entry, and the
pypiGitHub environment. Then I will archive the repository.Checklist