npm - @jjrawlins/cdk-diff-pr-github-action - Versions diffs - 0.0.6-beta → 0.0.6 - Mend

@jjrawlins/cdk-diff-pr-github-action 0.0.6-beta → 0.0.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (419) hide show

package/.yalc/@jjrawlins/cdk-diff-pr-github-action/.yalc/@jjrawlins/cdk-diff-pr-github-action/.yalc/@jjrawlins/cdk-diff-pr-github-action/.yalc/@jjrawlins/cdk-diff-pr-github-action/.yalc/@jjrawlins/cdk-diff-pr-github-action/.yalc/@jjrawlins/cdk-diff-pr-github-action/.yalc/@jjrawlins/cdk-diff-pr-github-action/.junie/guidelines.md DELETED Viewed

@@ -1,62 +0,0 @@
-### Guidelines
-## AWS Credentials and Environment Setup
-Use the .env file if there is one present
-### Steps
-1) Load environment variables for the chosen environment:
-```bash
-export $(grep -v '^#' .env | xargs)
-```
-2.) Verify credentials:
-```bash
-aws sts get-caller-identity
-```
-# Instructions for Projen Projects
-## Projen manages project config as code. Look for `.projenrc.<ext>` to understand how the project is defined.
-### Before you change anything
-- Locate `.projenrc.<ext>` (e.g., `.js`, `.ts`, `.py`).
-- Identify project type (Node, Python, etc.) and constructs used.
-- Check for existing Projen tasks that do what you need.
-### Typical workflow
-1) Update `.projenrc.*` with desired changes.
-2) Synthesize files:
-```bash
-npx projen
-```
-1) Review generated diffs before committing.
----
-## Memory-Aware Workflow (Mem0)
-Always check relevant memories before starting each task, and update them as needed. Follow this lightweight loop:
-1) Search for relevant memories
-    - Use concise keywords from the task (1–3 words). Example queries: `projen test`, `deploy creds`, `pytest flags`.
-    - If a relevant preference is found, apply it during the task.
-2) Add new preferences when discovered
-    - When you or the user clarify a repeatable preference or rule, store it as a memory in clear, actionable language.
-3) Verify memory storage (quick check)
-    - After adding a memory, immediately retrieve it with a related keyword to confirm it’s indexed and discoverable.
-4) Re-run with preference when applicable
-    - If the memory affects execution (e.g., which command to run), ensure the next step uses the remembered preference.
-### Example (validated)
-- Preference: "I prefer npx projen test when there is a .projenrc.ts file present in the project."
-- Retrieval keyword: `projen test preference`
-- Expected outcome: The preference is found and informs task execution (e.g., run `npx projen test` when `.projenrc.ts` exists).
----
-## Web Search
-Use the kagi mcp for web search related needs.  Especially when trying to find the latest documents to solve the current task problem.

@@ -1,3 +0,0 @@
-# ~~ Generated by projen. To modify, edit .projenrc.ts and run "npx projen".
-nodejs 20.9.0
-yarn 1.22.22