skills.rest
quickwit-oss
quickwit-ossOFFICIAL
Explore all skills by this author →
Website𝕏@Quickwit_IncGitHub

update-lambda

Automates lambda artifact release, build.rs update, and PR creation via GitHub Actions.

11.6k|585|Updated Apr 13, 2021
Search Tags:#release automation#Lambda#quickwit#build.rs#GitHub actions#gitHub cli#Pull request
One-click install
npx skills add https://github.com/quickwit-oss/quickwit --skill update-lambda
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-lambda
Source: https://github.com/quickwit-oss/quickwit/tree/main/.claude/skills/update-lambda
Command: npx skills add https://github.com/quickwit-oss/quickwit --skill update-lambda

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing a new Quickwit lambda artifact requires manually pushing tags, waiting for CI, copying artifact URLs and SHA256 hashes into build.rs, and opening a PR. This Skill automates that entire multi-step release workflow.

Core Features & Use Cases

  • Automated Release Triggering: Pushes a lambda-<commit> tag to trigger the Release Lambda binary GitHub Actions workflow and polls until it completes.
  • Artifact Metadata Update: Fetches the release asset URL and SHA256 digest, publishes the draft release, and updates LAMBDA_ZIP_URL and LAMBDA_ZIP_SHA256 in quickwit-lambda-client/build.rs.
  • PR Creation: Creates a branch, commits the change, and opens a pull request against quickwit-oss/quickwit.
  • Use Case: After merging lambda-related changes to main, run this Skill to cut a new lambda artifact release and open the corresponding build.rs update PR without manual steps.

Quick Start

Trigger a new lambda release from the current main branch and open a PR updating the build.rs artifact URL and hash.

Frequently Asked Questions about update-lambda

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I release a new Quickwit lambda artifact?▼

Push a tag named lambda-<commit-short-hash> to the repository, which triggers the Release Lambda binary GitHub Actions workflow. Once it succeeds, publish the draft release and update build.rs with the new artifact URL and SHA256.

How do I update the lambda artifact URL in build.rs?▼

Edit quickwit-lambda-client/build.rs and set LAMBDA_ZIP_URL to the release asset download URL and LAMBDA_ZIP_SHA256 to the bare SHA256 hex from the asset digest. These are the only two lines that change.

What happens if the lambda tag already exists?▼

If the lambda-<commit> tag already exists locally or on the remote, do not push a duplicate tag. Instead, skip directly to checking whether the corresponding workflow run and release already exist.

Why is the lambda release created as a draft?▼

The publish_lambda workflow creates the GitHub release as a draft by default. You must publish it with gh release edit --draft=false so build.rs can publicly download the artifact.

How long does the lambda release workflow take?▼

The Release Lambda binary workflow typically takes 15-20 minutes to complete. Poll the workflow runs with gh run list every 30 seconds until the run for your tag finishes.

Related Skills

Explore More Software Engineering Skills→
webdevcodywebdevcody
22

commit-push-and-release

Commit and push working-tree changes on main, then cut and push a minor version release tag.

Community
Intermediate
yahav123147yahav123147

land-and-deploy

Merge a pull request, wait for CI, deploy, and verify production with canary checks.

Community
Advanced
dodygdodyg

dotnet-github-releases

Create and manage GitHub Releases for .NET projects with tag-based workflows.

Community
Intermediate
kurojskurojs
2

homebrew-release

Automate GitHub release artifacts and Homebrew formula updates for tap releases.

Community
Intermediate