▸case-01 Our team needs an end-to-end package distribution framework for our enterprise libraries targeting Maven Central (`com.acme.core`) and the NuGet Gallery (`Acme.Core`). We require security signing for all artifacts, CDN distribution configuration, and post-deployment validation. Please produce the publishing scripts, artifact signature setup, verification test procedures, installation docs, and instructions on how to perform package rollbacks if a bad build gets pushed. | fail→pass | 43,567 | 41,876 | -4% | 1 | 1 | 0% | 8,277 | 8,320 | +1% | 0 | 0 | — |
▸case-02 We are releasing a JavaScript library `@acme/utils` to the public npm registry. Developers often forget the public access flag for scoped packages, causing npm publish to fail or default to private paid scope. Create a publishing script and checklist for this package. | pass→pass | 15,655 | 16,231 | +4% | 1 | 1 | 0% | 2,636 | 3,820 | +45% | 0 | 0 | — |
▸case-03 Configure a release pipeline for a Python package named `acme-analytics` sending builds to PyPI. Instead of relying on unsigned wheel uploads, ensure cryptographic verification is built into the automated release pipeline. | fail→fail | 22,182 | 25,420 | +15% | 1 | 1 | 0% | 3,288 | 5,566 | +69% | 0 | 0 | — |
▸case-04 Write a automation script for publishing a Rust library `acme-crate` to crates.io. Include a step that tests whether a fresh project can actually fetch and compile the newly published crate version from crates.io. | fail→pass | 15,834 | 23,099 | +46% | 1 | 1 | 0% | 3,067 | 4,012 | +31% | 0 | 0 | — |
▸case-05 Provide a publishing procedure for a C# library `Acme.Engine` to NuGet.org using the `dotnet nuget push` CLI. Ensure package integrity signing is performed so consumers can verify author identity. | pass→pass | 13,400 | 25,968 | +94% | 1 | 1 | 0% | 2,645 | 4,773 | +80% | 0 | 0 | — |
▸case-06 Our product lifecycle requires releasing early builds to `alpha` and `beta` channels before promoting to `stable`. Show how to structure the distribution strategy and registry target configurations across these three channels for an npm package. | pass→pass | 22,285 | 22,906 | +3% | 1 | 1 | 0% | 3,257 | 3,797 | +17% | 0 | 0 | — |
▸case-07 A broken release `@acme/core@2.1.0` was accidentally published to npm 10 minutes ago. Provide the emergency operations playbook to prevent users from installing this broken version while maintaining package integrity. | pass→pass | 20,920 | 24,955 | +19% | 1 | 1 | 0% | 2,771 | 4,077 | +47% | 0 | 0 | — |
▸case-08 A critical bug was discovered in `acme-tool` version 1.4.2 on PyPI after release. Since PyPI does not allow re-using version numbers or simple deletion, outline the precise registry mechanism to invalidate this version for dependency resolvers without breaking existing pin locks. | pass→pass | 13,024 | 17,127 | +32% | 1 | 1 | 0% | 2,028 | 2,471 | +22% | 0 | 0 | — |
▸case-09 Set up a publishing workflow for `com.acme.sdk:auth` targeting Maven Central via Sonatype OSSRH. The team wants to ensure the staging repository is automatically closed and dropped or released upon verification failures. | fail→pass | 18,483 | 27,199 | +47% | 1 | 1 | 0% | 3,549 | 6,102 | +72% | 0 | 0 | — |
▸case-10 We distribute static browser bundles of `@acme/ui` via a global CDN mirror (e.g., Cloudflare / Fastly) alongside npm. After pushing a new version to npm, users report seeing stale assets on the CDN. Provide the pipeline step to resolve this CDN sync issue. | pass→pass | 38,634 | 23,863 | -38% | 1 | 1 | 0% | 2,332 | 4,144 | +78% | 0 | 0 | — |
▸case-11 We want to publish both npm (`@acme/core`) and Maven (`com.acme:core`) packages to GitHub Packages. Provide the credential configuration setup for both package managers to authenticate during deployment. | pass→pass | 12,387 | 19,380 | +56% | 1 | 1 | 0% | 2,564 | 3,510 | +37% | 0 | 0 | — |
▸case-12 Create a post-publish validation runner for PyPI package `acme-cli` that guarantees the package is installable in a clean Linux environment without cached local artifacts. | pass→pass | 22,369 | 27,818 | +24% | 1 | 1 | 0% | 3,599 | 5,069 | +41% | 0 | 0 | — |
▸case-13 We are establishing package publishing conventions for our JavaScript libraries. Developers frequently submit un-namespaced package names like `analytics-lib` which cause conflicts on public registries. Draft a policy and package configuration for scope enforcement. | pass→pass | 19,953 | 15,698 | -21% | 1 | 1 | 0% | 2,337 | 3,461 | +48% | 0 | 0 | — |
▸case-14 Set up a CI release job for Cargo publishing of `acme-parser`. Make sure credentials are not leaked in build logs and the release package is verified locally before final registry upload. | pass→pass | 17,478 | 17,764 | +2% | 1 | 1 | 0% | 2,396 | 3,801 | +59% | 0 | 0 | — |
▸case-15 When publishing `Acme.Data` to NuGet, downstream developers need to debug into our source code. Configure the build and publish script to produce and upload debugging symbols alongside the main binary. | pass→pass | 12,785 | 23,038 | +80% | 1 | 1 | 0% | 2,348 | 3,976 | +69% | 0 | 0 | — |
▸case-16 Generate standard end-user installation documentation templates for a multi-language SDK provided as `acme-sdk` across npm, PyPI, and Maven Central. | pass→pass | 14,551 | 27,281 | +87% | 1 | 1 | 0% | 2,784 | 4,814 | +73% | 0 | 0 | — |
▸case-17 Our GPG signing key used for signing Maven Central JARs and PyPI wheels is expiring. Outline the step-by-step key rotation process for our automated publishing service account. | pass→pass | 24,253 | 20,426 | -16% | 1 | 1 | 0% | 3,498 | 4,095 | +17% | 0 | 0 | — |
▸case-18 A security flaw was detected in `acme-crypto` version 0.3.1 on crates.io. Write the CLI execution steps to yank this release and document the impact on existing Cargo.lock files. | fail→fail | 9,915 | 13,260 | +34% | 1 | 1 | 0% | 1,830 | 2,813 | +54% | 0 | 0 | — |
▸case-19 Provide the Maven `pom.xml` plugin execution configuration required to automatically sign all JAR artifacts (main, sources, javadoc) during the release lifecycle. | pass→pass | 9,768 | 9,561 | -2% | 1 | 1 | 0% | 1,933 | 2,241 | +16% | 0 | 0 | — |
▸case-20 We need a script that analyzes git commit messages following Conventional Commits format (`feat:`, `fix:`, `BREAKING CHANGE:`) and computes the next SemVer version number string for our repository. Provide the version calculation script. | pass→pass | 20,541 | 30,761 | +50% | 1 | 1 | 0% | 4,304 | 6,744 | +57% | 0 | 0 | — |
▸case-21 Configure a CI pipeline task to build a multi-architecture Docker image using Buildx and push it to Amazon ECR (`123456789.dkr.ecr.us-east-1.amazonaws.com/acme-app:v1.2.0`). Include IAM login steps. | pass→pass | 17,340 | 17,939 | +3% | 1 | 1 | 0% | 2,714 | 4,443 | +64% | 0 | 0 | — |
▸case-22 Write a Jest and PyTest configuration file that runs unit tests, generates LCOV coverage reports, and enforces a strict threshold of 85% line coverage during pull request builds. | pass→pass | 12,006 | 18,307 | +52% | 1 | 1 | 0% | 2,349 | 2,986 | +27% | 0 | 0 | — |