[PR #459] [MERGED] test(package): verify npx upgrade on published releases #2005

Closed
opened 2026-10-16 21:13:18 +00:00 by bsakaguchi · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/459
Author: @morluto
Created: 8/1/2026
Status: ✅ Merged
Merged: 8/1/2026
Merged by: @morluto

Base: main ← Head: agent/verify-npx-upgrade-e2e


📝 Commits (1)

  • 1f8ad7b test(package): verify npx upgrade on published releases

📊 Changes

1 file changed (+104 additions, -4 deletions)

View changed files

📝 scripts/verify-published-package.mjs (+104 -4)

📄 Description

Description

Add a published-package end-to-end check for the user-facing npx rea-agents upgrade path.

The verifier installs the highest published release below the target into an isolated npm prefix, runs npx rea-agents upgrade --json, confirms the global package was replaced by the target release, and starts the upgraded executable. This keeps the check independent of the developer's global npm installation and exercises real npm package resolution.

Type of Change

  • Bug fix
  • New feature
  • Documentation update
  • Performance improvement
  • Refactoring (no functional change)
  • Tooling/test coverage
  • Tool contract change (MCP schema modification)

Testing Performed

  • TypeScript typecheck passes (npm run typecheck)
  • Linting passes (npm run lint; five pre-existing warnings, zero errors)
  • Full test suite passes (npm test)
  • Real Hopper verification performed (npm run verify:hopper)
  • Linux real Hopper verification performed
  • Real browser verification performed
  • Package verification performed (npm run verify:package)
  • Published-package E2E passes: node scripts/verify-published-package.mjs 2.5.0 (2.4.0 → 2.5.0, installed version and executable startup confirmed)

Tool Contract Impact

None.

None.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/459 **Author:** [@morluto](https://github.com/morluto) **Created:** 8/1/2026 **Status:** ✅ Merged **Merged:** 8/1/2026 **Merged by:** [@morluto](https://github.com/morluto) **Base:** `main` ← **Head:** `agent/verify-npx-upgrade-e2e` --- ### 📝 Commits (1) - [`1f8ad7b`](https://github.com/morluto/rea/commit/1f8ad7bc68f50d396715116467f19524da7e05e6) test(package): verify npx upgrade on published releases ### 📊 Changes **1 file changed** (+104 additions, -4 deletions) <details> <summary>View changed files</summary> 📝 `scripts/verify-published-package.mjs` (+104 -4) </details> ### 📄 Description ## Description Add a published-package end-to-end check for the user-facing `npx rea-agents upgrade` path. The verifier installs the highest published release below the target into an isolated npm prefix, runs `npx rea-agents upgrade --json`, confirms the global package was replaced by the target release, and starts the upgraded executable. This keeps the check independent of the developer's global npm installation and exercises real npm package resolution. ## Type of Change - [ ] Bug fix - [ ] New feature - [ ] Documentation update - [ ] Performance improvement - [ ] Refactoring (no functional change) - [x] Tooling/test coverage - [ ] Tool contract change (MCP schema modification) ## Testing Performed - [x] TypeScript typecheck passes (`npm run typecheck`) - [x] Linting passes (`npm run lint`; five pre-existing warnings, zero errors) - [ ] Full test suite passes (`npm test`) - [ ] Real Hopper verification performed (`npm run verify:hopper`) - [ ] Linux real Hopper verification performed - [ ] Real browser verification performed - [ ] Package verification performed (`npm run verify:package`) - [x] Published-package E2E passes: `node scripts/verify-published-package.mjs 2.5.0` (`2.4.0 → 2.5.0`, installed version and executable startup confirmed) ## Tool Contract Impact None. ## Related Issues None. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-16 21:13:18 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#2005
No description provided.