@sentry/junior-maintenance 0.70.0

package/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+   any Contribution intentionally submitted for inclusion in the Work
+   by You to the Licensor shall be under the terms and conditions of
+   this License, without any additional terms or conditions.
+   Notwithstanding the above, nothing herein shall supersede or modify
+   the terms of any separate license agreement you may have executed
+   with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+   names, trademarks, service marks, or product names of the Licensor,
+   except as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+   agreed to in writing, Licensor provides the Work (and each
+   Contributor provides its Contributions) on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+   implied, including, without limitation, any warranties or conditions
+   of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+   PARTICULAR PURPOSE. You are solely responsible for determining the
+   appropriateness of using or redistributing the Work and assume any
+   risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+   whether in tort (including negligence), contract, or otherwise,
+   unless required by applicable law (such as deliberate and grossly
+   negligent acts) or agreed to in writing, shall any Contributor be
+   liable to You for damages, including any direct, indirect, special,
+   incidental, or consequential damages of any character arising as a
+   result of this License or out of the use or inability to use the
+   Work (including but not limited to damages for loss of goodwill,
+   work stoppage, computer failure or malfunction, or any and all
+   other commercial damages or losses), even if such Contributor
+   has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+   the Work or Derivative Works thereof, You may choose to offer,
+   and charge a fee for, acceptance of support, warranty, indemnity,
+   or other liability obligations and/or rights consistent with this
+   License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf
+   of any other Contributor, and only if You agree to indemnify,
+   defend, and hold each Contributor harmless for any liability
+   incurred by, or claims asserted against, such Contributor by reason
+   of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,26 @@
+# @sentry/junior-maintenance
+
+Junior maintenance plugin — skills for keeping Junior apps up to date and healthy.
+
+## Skills
+
+### `self-update`
+
+Updates `@sentry/junior` and `@sentry/junior-*` dependencies in a Junior consumer app to the latest published release. Handles version resolution, lockfile sync, safety checks, and opens a draft PR.
+
+## Usage
+
+Install the package and register it in `plugins.ts`:
+
+```bash
+pnpm add @sentry/junior-maintenance
+```
+
+```ts
+import { defineJuniorPlugins } from "@sentry/junior";
+
+export const plugins = defineJuniorPlugins([
+  // ... other plugins
+  "@sentry/junior-maintenance",
+]);
+```

package/package.json

@@ -0,0 +1,19 @@
+{
+  "name": "@sentry/junior-maintenance",
+  "version": "0.70.0",
+  "private": false,
+  "publishConfig": {
+    "access": "public"
+  },
+  "type": "module",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/getsentry/junior.git",
+    "directory": "packages/junior-maintenance"
+  },
+  "files": [
+    "plugin.yaml",
+    "skills",
+    "README.md"
+  ]
+}

package/plugin.yaml

@@ -0,0 +1,2 @@
+name: maintenance
+description: Junior maintenance workflows for updating and improving Junior apps

package/skills/self-update/SKILL.md

@@ -0,0 +1,229 @@
+---
+name: self-update
+description: Update this junior-prod app to the latest published Junior release. Use when asked to self-update Junior, bump @sentry/junior and @sentry/junior-* dependencies, run safety checks, and open a draft PR.
+---
+
+## Workflow
+
+### 1. Preflight
+
+```bash
+git status --short
+git branch --show-current
+```
+
+Stop if `package.json`, `pnpm-lock.yaml`, or `pnpm-workspace.yaml` has unrelated uncommitted changes.
+
+### 2. Inventory deps
+
+Collect direct Junior deps from `package.json` — `@sentry/junior` and names starting with `@sentry/junior-`. Record each package's name, current version, and dependency section (`dependencies` / `devDependencies` / `optionalDependencies`). All must be pinned to the same exact version. Do not move packages between sections.
+
+### 3. Resolve target
+
+```bash
+pnpm view @sentry/junior dist-tags.latest
+```
+
+If user requests a specific version, use that. If already on latest, stop.
+
+Verify the target exists for every inventoried package before mutating files:
+
+```bash
+pnpm view <package>@<target> version
+```
+
+Stop if any package lacks the target on npm.
+
+### 3b. Build Junior release context
+
+Junior does not publish GitHub releases, git tags, or a CHANGELOG. Build a best-effort release summary to guide the update and populate the PR body.
+
+1. Note `old_version` (current `@sentry/junior` from step 2) and `target_version` (from step 3).
+
+2. Fetch npm publish timestamps:
+
+   ```bash
+   pnpm view @sentry/junior time --json
+   ```
+
+   Extract `old_published_at` and `target_published_at` from the result.
+
+3. Query merged PRs in `getsentry/junior` between those timestamps:
+
+   ```bash
+   gh pr list --repo getsentry/junior --state merged \
+     --search "merged:>=<old_published_at> merged:<=<target_published_at>" \
+     --limit 100 \
+     --json number,title,url,mergedAt
+   ```
+
+4. Classify the results:
+   - **Breaking:** PR titles matching `^[a-z]+([^)]*)!:` (conventional-commit `!` marker), or body containing `BREAKING CHANGE`.
+   - **Config-relevant:** titles/scopes mentioning `config`, `plugins`, `nitro`, `createApp`, `runtime`, `credentials`, `egress`, or `example`.
+
+5. Save a compact summary — total PR count, breaking PRs (title + URL), config-relevant PRs — for the PR body. Do not list every fix/chore PR.
+
+6. If breaking PRs are found, flag the update as needing manual review in the PR body and keep the PR draft. Do **not** abort the update — proceed and let checks and the config comparison (step 6c) surface concrete issues.
+
+### 4. Create or reuse branch
+
+`build/update-junior-<target>`. All file mutations happen on this branch.
+
+### 5. Sync `minimumReleaseAgeExclude`
+
+If `pnpm-workspace.yaml` has a `minimumReleaseAgeExclude` list, ensure every Junior package from step 2 is listed. Add missing entries before `pnpm add`. Append at end, preserve existing order.
+
+### 6. Update deps (section-preserving)
+
+Group `pnpm add` by dependency section:
+
+| Section | Flag |
+|---------|------|
+| `dependencies` | `-E` |
+| `devDependencies` | `-D -E` |
+| `optionalDependencies` | `-O -E` |
+
+```bash
+pnpm add -E <deps-packages>@<target> ...
+pnpm add -D -E <devDeps-packages>@<target> ...   # if any
+pnpm add -O -E <optDeps-packages>@<target> ...    # if any
+```
+
+Do not manually edit versions in `package.json`. Do not use local `../junior` linking scripts.
+
+### 6b. Sync `nitro.config.ts` plugin packages
+
+After updating deps, check whether any **new** `@sentry/junior-*` packages were added (i.e. present in the new `package.json` but absent before the update). For each newly added package, ensure it is also listed in the `plugins.packages` array inside `juniorNitro({...})` in `nitro.config.ts`.
+
+**Packages that are NOT standalone plugins and do NOT need a `plugins.packages` entry:**
+- `@sentry/junior` (the base runtime)
+- `@sentry/junior-plugin-api` (plugin development utilities)
+- `@sentry/junior-testing` (test utilities)
+
+For every other newly added `@sentry/junior-*` package, add it to `nitro.config.ts` if missing:
+
+```typescript
+// nitro.config.ts — append the new package to plugins.packages
+juniorNitro({
+  plugins: { packages: [
+    // ... existing entries ...
+    "@sentry/junior-<new-package>",  // ← add here
+  ] },
+})
+```
+
+Verify by running:
+
+```bash
+node scripts/check-plugin-packages.mjs
+```
+
+This must exit 0 before proceeding. If it fails, fix `nitro.config.ts` and rerun.
+
+### 6c. Compare consumer config against the Junior example app
+
+After updating deps, compare this app's configuration files against `apps/example/` in `getsentry/junior` for the target version. Goal: catch config-shape drift before checks run.
+
+1. Clone `getsentry/junior` into a temp directory (skip if already present from a prior run):
+
+   ```bash
+   git clone --filter=blob:none --depth=200 https://github.com/getsentry/junior.git /tmp/junior-upstream
+   cd /tmp/junior-upstream
+   ```
+
+2. Select the best source ref for `target_version`:
+
+   a. Try to find the version-bump commit:
+      ```bash
+      git log --oneline -S'"version": "<target_version>"' -- packages/junior/package.json
+      ```
+      If found, check out that commit.
+
+   b. If not found, find the commit just before the npm publish timestamp:
+      ```bash
+      git rev-list -n 1 --before="<target_published_at>" origin/main
+      ```
+      If found, check out that commit.
+
+   c. If neither works, use `origin/main` — mark the comparison as approximate in the PR body.
+
+3. Run focused diffs between example app and consumer app:
+
+   ```bash
+   git diff --no-index -- /tmp/junior-upstream/apps/example/nitro.config.ts nitro.config.ts
+   git diff --no-index -- /tmp/junior-upstream/apps/example/plugins.ts plugins.ts
+   git diff --no-index -- /tmp/junior-upstream/apps/example/server.ts server.ts
+   ```
+
+4. Interpret the diffs structurally. Look for changes in:
+   - `juniorNitro()` option shape (new/removed/renamed options)
+   - `defineJuniorPlugins([...])` usage or call convention
+   - Plugin factory call signatures (e.g. `githubPlugin({ ... })`)
+   - `createApp({ ... })` option keys
+   - Required support devDeps (`nitro`, `jiti`, `typescript`)
+
+   **Ignore** app-local differences: env var names, local plugin/skill registrations, custom config defaults, SOUL/WORLD content, Slack personality settings.
+
+5. Apply only obvious, low-risk fixes automatically — e.g. updating a renamed option key or adding a required new argument when the value is inferrable. For everything else, add a PR-body action item.
+
+6. For `package.json`, compare only the build tooling (`nitro`, `jiti`, `typescript`) — do not copy the example's plugin dep list or version pins.
+
+7. Save findings and any actions taken for the PR body.
+
+### 7. Verify lockfile correctness
+
+1. Check changed files:
+   ```bash
+   git diff --name-only
+   ```
+   Expected: `package.json`, `pnpm-lock.yaml`, optionally `pnpm-workspace.yaml`, and optionally `nitro.config.ts` if plugin registration changed in step 6b. Flag anything else.
+
+2. Confirm every Junior dep in `package.json` shows exact `<target>` — no old versions remain.
+
+3. Prove lockfile agrees with package.json:
+   ```bash
+   pnpm install --frozen-lockfile
+   ```
+   If this fails, repair with `pnpm install --lockfile-only` then rerun. Stop if still broken.
+
+### 8. Run checks
+
+```bash
+pnpm check
+pnpm typecheck
+pnpm build
+```
+
+Classify failures: update-related → fix before PR; pre-existing or environment → capture in PR and disclose. Do not silently skip failed checks.
+
+### 9. Commit
+
+```text
+build(deps): Update Junior packages to <target>
+
+Update the Junior runtime and plugin packages to <target> and refresh the pnpm lockfile.
+```
+
+Mention `minimumReleaseAgeExclude` sync if `pnpm-workspace.yaml` changed.
+
+### 10. Push and open/update draft PR
+
+PR body sections (in order):
+
+1. **Version change** — old → new, package list with sections.
+2. **Junior release window** — total PR count, breaking PRs (title + URL), config-relevant PRs. Sourced from step 3b. Include the disclaimer: _Junior does not publish GitHub releases, tags, or a changelog. This summary is derived from npm publish timestamps and merged PRs._
+3. **Example app config comparison** — source ref used (commit SHA or approximate), files compared, findings, actions taken. Sourced from step 6c.
+4. **`minimumReleaseAgeExclude` changes** (if any).
+5. **`nitro.config.ts` plugin registration changes** (if any).
+6. **Check results** — pass/fail per check, pre-existing failures noted.
+7. **Unexpected diffs** — any changed files beyond `package.json`, `pnpm-lock.yaml`, `pnpm-workspace.yaml`, `nitro.config.ts`.
+
+If breaking PRs were found in step 3b, or config comparison found unresolved drift, or checks failed — keep the PR as draft and add a "Manual review required" section at the top summarizing blockers.
+
+## Stop conditions
+
+- Any Junior package lacks the target version on npm.
+- `pnpm install --frozen-lockfile` fails after repair.
+- Checks fail for non-pre-existing, non-environment reasons and no safe config fix is available from step 6c.
+- `package.json` changed but `pnpm-lock.yaml` did not.
+- Example app comparison reveals a breaking plugin signature change whose required values cannot be inferred from the existing consumer config.