Add workflow to build and release scraper binary#3556
Merged
cuihtlauac merged 1 commit intomainfrom Mar 10, 2026
Merged
Conversation
When tool/ or src/ changes on main, build the scraper and publish it as a GitHub release (scraper-latest). This avoids rebuilding the OCaml toolchain on every daily scrape run. Co-Authored-By: Claude Opus 4.6 <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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
release-scrapers.ymlworkflow that builds the scraper binary and publishes it as ascraper-latestGitHub releasemainthat touchtool/**,src/**,dune-project, or*.opamworkflow_dispatchfor manual bootstrappingTest plan
release-scrapers.ymlmanually via workflow_dispatchscraper-latestrelease is created withscrape.exeasset🤖 Generated with Claude Code