diff --git a/.amazonq/rules/project.md b/.amazonq/rules/project.md new file mode 100644 index 0000000..efd17c8 --- /dev/null +++ b/.amazonq/rules/project.md @@ -0,0 +1,51 @@ +# Projen-managed Project Instructions + +This project is managed by [projen](https://github.com/projen/projen), a project configuration management tool. + +## Important Guidelines + +### Task Execution + +- **Always use projen for task execution**: Run tasks using `npx projen ` instead of directly using npm, yarn, or other package managers. +- **Check available tasks**: Look in `.projen/tasks.json` to see all available tasks, their descriptions, and steps. +- **Common tasks**: + - `npx projen` - Synthesize project configuration files + - `npx projen build` - Builds the project, including running tests + - `npx projen test` - Runs tests only + - `npx projen compile` - Compiles the source code only + +### File Modifications + +- **DO NOT manually edit generated files**: Files marked with a comment like "~~ Generated by projen. To modify..." should never be edited directly. +- **Modify configuration in .projenrc**: To change project configuration, always edit the `.projenrc.ts`, `.projenrc.py` or `.projenrc.json` etc. file and then run `npx projen` to regenerate the project files. +- **Check .projenrc first**: Before suggesting changes to package.json, tsconfig.json, or other configuration files, always check if these are managed by projen and suggest changes to .projenrc instead. + +### Dependencies + +- **Add dependencies through projen**: Use the projen configuration to add dependencies instead of manually editing package.json or using npm/yarn install directly. +- **Example**: In .projenrc, use methods like `addDeps()`, `addDevDeps()`, or `addPeerDeps()` to add dependencies. + +### Workflow + +1. Make changes to .projenrc configuration file +2. Run `npx projen` to synthesize and update generated files +3. Review the changes +4. Commit both .projenrc and the generated files + +## Projen Configuration + +This project's configuration is defined in the .projenrc file at the root of the repository. All project metadata, dependencies, scripts, and tooling configuration should be managed through this file. + +## Additional Resources + +- [Projen Documentation](https://projen.io) +- [Projen GitHub Repository](https://github.com/projen/projen) + +# Development Best Practices + +- **Always run build after changes**: After modifying any source or test file, run `npx projen build` to ensure your changes compile and pass all tests. +- **Task completion criteria**: A task is not considered complete until: + - All tests pass (`npx projen test`) + - There are no compilation errors (`npx projen compile`) + - There are no linting errors (usually part of the build, if not, run the linter defined in tasks.json) + - The full build succeeds (`npx projen build`) diff --git a/.cursor/rules/project.md b/.cursor/rules/project.md new file mode 100644 index 0000000..efd17c8 --- /dev/null +++ b/.cursor/rules/project.md @@ -0,0 +1,51 @@ +# Projen-managed Project Instructions + +This project is managed by [projen](https://github.com/projen/projen), a project configuration management tool. + +## Important Guidelines + +### Task Execution + +- **Always use projen for task execution**: Run tasks using `npx projen ` instead of directly using npm, yarn, or other package managers. +- **Check available tasks**: Look in `.projen/tasks.json` to see all available tasks, their descriptions, and steps. +- **Common tasks**: + - `npx projen` - Synthesize project configuration files + - `npx projen build` - Builds the project, including running tests + - `npx projen test` - Runs tests only + - `npx projen compile` - Compiles the source code only + +### File Modifications + +- **DO NOT manually edit generated files**: Files marked with a comment like "~~ Generated by projen. To modify..." should never be edited directly. +- **Modify configuration in .projenrc**: To change project configuration, always edit the `.projenrc.ts`, `.projenrc.py` or `.projenrc.json` etc. file and then run `npx projen` to regenerate the project files. +- **Check .projenrc first**: Before suggesting changes to package.json, tsconfig.json, or other configuration files, always check if these are managed by projen and suggest changes to .projenrc instead. + +### Dependencies + +- **Add dependencies through projen**: Use the projen configuration to add dependencies instead of manually editing package.json or using npm/yarn install directly. +- **Example**: In .projenrc, use methods like `addDeps()`, `addDevDeps()`, or `addPeerDeps()` to add dependencies. + +### Workflow + +1. Make changes to .projenrc configuration file +2. Run `npx projen` to synthesize and update generated files +3. Review the changes +4. Commit both .projenrc and the generated files + +## Projen Configuration + +This project's configuration is defined in the .projenrc file at the root of the repository. All project metadata, dependencies, scripts, and tooling configuration should be managed through this file. + +## Additional Resources + +- [Projen Documentation](https://projen.io) +- [Projen GitHub Repository](https://github.com/projen/projen) + +# Development Best Practices + +- **Always run build after changes**: After modifying any source or test file, run `npx projen build` to ensure your changes compile and pass all tests. +- **Task completion criteria**: A task is not considered complete until: + - All tests pass (`npx projen test`) + - There are no compilation errors (`npx projen compile`) + - There are no linting errors (usually part of the build, if not, run the linter defined in tasks.json) + - The full build succeeds (`npx projen build`) diff --git a/.gitattributes b/.gitattributes index 0326c9d..241657a 100644 --- a/.gitattributes +++ b/.gitattributes @@ -2,8 +2,11 @@ * text=auto eol=lf *.snap linguist-generated -/.eslintrc.json linguist-generated +/.amazonq/rules/project.md linguist-generated +/.cursor/rules/project.md linguist-generated +/.eslintrc.json linguist-generated linguist-language=JSON-with-Comments /.gitattributes linguist-generated +/.github/copilot-instructions.md linguist-generated /.github/pull_request_template.md linguist-generated /.github/workflows/add-to-project.yml linguist-generated /.github/workflows/add-to-update-projen-project.yml linguist-generated @@ -14,6 +17,7 @@ /.github/workflows/renovate.yml linguist-generated /.github/workflows/update-projen-main.yml linguist-generated /.gitignore linguist-generated +/.kiro/steering/project.md linguist-generated /.mergify.yml linguist-generated /.npmignore linguist-generated /.npmrc linguist-generated @@ -24,8 +28,10 @@ /.projen/deps.json linguist-generated /.projen/files.json linguist-generated /.projen/tasks.json linguist-generated +/AGENTS.md linguist-generated /API.md linguist-generated +/CLAUDE.md linguist-generated /package.json linguist-generated /pnpm-lock.yaml linguist-generated -/renovate.json5 linguist-generated -/tsconfig.dev.json linguist-generated \ No newline at end of file +/renovate.json5 linguist-generated linguist-language=JSON-with-Comments +/tsconfig.dev.json linguist-generated linguist-language=JSON-with-Comments \ No newline at end of file diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md new file mode 100644 index 0000000..efd17c8 --- /dev/null +++ b/.github/copilot-instructions.md @@ -0,0 +1,51 @@ +# Projen-managed Project Instructions + +This project is managed by [projen](https://github.com/projen/projen), a project configuration management tool. + +## Important Guidelines + +### Task Execution + +- **Always use projen for task execution**: Run tasks using `npx projen ` instead of directly using npm, yarn, or other package managers. +- **Check available tasks**: Look in `.projen/tasks.json` to see all available tasks, their descriptions, and steps. +- **Common tasks**: + - `npx projen` - Synthesize project configuration files + - `npx projen build` - Builds the project, including running tests + - `npx projen test` - Runs tests only + - `npx projen compile` - Compiles the source code only + +### File Modifications + +- **DO NOT manually edit generated files**: Files marked with a comment like "~~ Generated by projen. To modify..." should never be edited directly. +- **Modify configuration in .projenrc**: To change project configuration, always edit the `.projenrc.ts`, `.projenrc.py` or `.projenrc.json` etc. file and then run `npx projen` to regenerate the project files. +- **Check .projenrc first**: Before suggesting changes to package.json, tsconfig.json, or other configuration files, always check if these are managed by projen and suggest changes to .projenrc instead. + +### Dependencies + +- **Add dependencies through projen**: Use the projen configuration to add dependencies instead of manually editing package.json or using npm/yarn install directly. +- **Example**: In .projenrc, use methods like `addDeps()`, `addDevDeps()`, or `addPeerDeps()` to add dependencies. + +### Workflow + +1. Make changes to .projenrc configuration file +2. Run `npx projen` to synthesize and update generated files +3. Review the changes +4. Commit both .projenrc and the generated files + +## Projen Configuration + +This project's configuration is defined in the .projenrc file at the root of the repository. All project metadata, dependencies, scripts, and tooling configuration should be managed through this file. + +## Additional Resources + +- [Projen Documentation](https://projen.io) +- [Projen GitHub Repository](https://github.com/projen/projen) + +# Development Best Practices + +- **Always run build after changes**: After modifying any source or test file, run `npx projen build` to ensure your changes compile and pass all tests. +- **Task completion criteria**: A task is not considered complete until: + - All tests pass (`npx projen test`) + - There are no compilation errors (`npx projen compile`) + - There are no linting errors (usually part of the build, if not, run the linter defined in tasks.json) + - The full build succeeds (`npx projen build`) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index 335c8d2..1fd20f8 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -41,11 +41,6 @@ jobs: run: pnpm i --no-frozen-lockfile - name: build run: npx projen build - - name: Upload coverage to Codecov - uses: codecov/codecov-action@v5 - with: - token: ${{ secrets.CODECOV_TOKEN }} - directory: coverage - name: Find mutations id: self_mutation run: |- diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index efa2575..0c7e941 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -50,11 +50,6 @@ jobs: run: pnpm i --frozen-lockfile - name: release run: npx projen release - - name: Upload coverage to Codecov - uses: codecov/codecov-action@v5 - with: - token: ${{ secrets.CODECOV_TOKEN }} - directory: coverage - name: Check if version has already been tagged id: check_tag_exists run: |- diff --git a/.gitignore b/.gitignore index e148b8f..4143ae3 100644 --- a/.gitignore +++ b/.gitignore @@ -43,8 +43,6 @@ junit.xml /dist/changelog.md /dist/version.txt !/.github/workflows/release.yml -codecov -codecov.* !/.mergify.yml !/.github/pull_request_template.md !/.prettierignore @@ -64,4 +62,10 @@ tsconfig.json !/.github/workflows/add-to-project.yml !/.github/workflows/update-projen-main.yml !/.github/workflows/add-to-update-projen-project.yml +!/.github/copilot-instructions.md +!/.cursor/rules/project.md +!/CLAUDE.md +!/.amazonq/rules/project.md +!/.kiro/steering/project.md +!/AGENTS.md !/.projenrc.ts diff --git a/.kiro/steering/project.md b/.kiro/steering/project.md new file mode 100644 index 0000000..efd17c8 --- /dev/null +++ b/.kiro/steering/project.md @@ -0,0 +1,51 @@ +# Projen-managed Project Instructions + +This project is managed by [projen](https://github.com/projen/projen), a project configuration management tool. + +## Important Guidelines + +### Task Execution + +- **Always use projen for task execution**: Run tasks using `npx projen ` instead of directly using npm, yarn, or other package managers. +- **Check available tasks**: Look in `.projen/tasks.json` to see all available tasks, their descriptions, and steps. +- **Common tasks**: + - `npx projen` - Synthesize project configuration files + - `npx projen build` - Builds the project, including running tests + - `npx projen test` - Runs tests only + - `npx projen compile` - Compiles the source code only + +### File Modifications + +- **DO NOT manually edit generated files**: Files marked with a comment like "~~ Generated by projen. To modify..." should never be edited directly. +- **Modify configuration in .projenrc**: To change project configuration, always edit the `.projenrc.ts`, `.projenrc.py` or `.projenrc.json` etc. file and then run `npx projen` to regenerate the project files. +- **Check .projenrc first**: Before suggesting changes to package.json, tsconfig.json, or other configuration files, always check if these are managed by projen and suggest changes to .projenrc instead. + +### Dependencies + +- **Add dependencies through projen**: Use the projen configuration to add dependencies instead of manually editing package.json or using npm/yarn install directly. +- **Example**: In .projenrc, use methods like `addDeps()`, `addDevDeps()`, or `addPeerDeps()` to add dependencies. + +### Workflow + +1. Make changes to .projenrc configuration file +2. Run `npx projen` to synthesize and update generated files +3. Review the changes +4. Commit both .projenrc and the generated files + +## Projen Configuration + +This project's configuration is defined in the .projenrc file at the root of the repository. All project metadata, dependencies, scripts, and tooling configuration should be managed through this file. + +## Additional Resources + +- [Projen Documentation](https://projen.io) +- [Projen GitHub Repository](https://github.com/projen/projen) + +# Development Best Practices + +- **Always run build after changes**: After modifying any source or test file, run `npx projen build` to ensure your changes compile and pass all tests. +- **Task completion criteria**: A task is not considered complete until: + - All tests pass (`npx projen test`) + - There are no compilation errors (`npx projen compile`) + - There are no linting errors (usually part of the build, if not, run the linter defined in tasks.json) + - The full build succeeds (`npx projen build`) diff --git a/.npmignore b/.npmignore index 5e8ae35..0696454 100644 --- a/.npmignore +++ b/.npmignore @@ -24,6 +24,12 @@ dist tsconfig.tsbuildinfo /.eslintrc.json !.jsii +.github/copilot-instructions.md +.cursor/rules/project.md +CLAUDE.md +.amazonq/rules/project.md +.kiro/steering/project.md +AGENTS.md /.gitattributes /.projenrc.ts /projenrc diff --git a/.projen/files.json b/.projen/files.json index 4bcfcff..54ce828 100644 --- a/.projen/files.json +++ b/.projen/files.json @@ -1,7 +1,10 @@ { "files": [ + ".amazonq/rules/project.md", + ".cursor/rules/project.md", ".eslintrc.json", ".gitattributes", + ".github/copilot-instructions.md", ".github/pull_request_template.md", ".github/workflows/add-to-project.yml", ".github/workflows/add-to-update-projen-project.yml", @@ -12,6 +15,7 @@ ".github/workflows/renovate.yml", ".github/workflows/update-projen-main.yml", ".gitignore", + ".kiro/steering/project.md", ".mergify.yml", ".npmrc", ".nvmrc", @@ -20,6 +24,8 @@ ".projen/deps.json", ".projen/files.json", ".projen/tasks.json", + "AGENTS.md", + "CLAUDE.md", "renovate.json5", "tsconfig.dev.json" ], diff --git a/AGENTS.md b/AGENTS.md new file mode 100644 index 0000000..efd17c8 --- /dev/null +++ b/AGENTS.md @@ -0,0 +1,51 @@ +# Projen-managed Project Instructions + +This project is managed by [projen](https://github.com/projen/projen), a project configuration management tool. + +## Important Guidelines + +### Task Execution + +- **Always use projen for task execution**: Run tasks using `npx projen ` instead of directly using npm, yarn, or other package managers. +- **Check available tasks**: Look in `.projen/tasks.json` to see all available tasks, their descriptions, and steps. +- **Common tasks**: + - `npx projen` - Synthesize project configuration files + - `npx projen build` - Builds the project, including running tests + - `npx projen test` - Runs tests only + - `npx projen compile` - Compiles the source code only + +### File Modifications + +- **DO NOT manually edit generated files**: Files marked with a comment like "~~ Generated by projen. To modify..." should never be edited directly. +- **Modify configuration in .projenrc**: To change project configuration, always edit the `.projenrc.ts`, `.projenrc.py` or `.projenrc.json` etc. file and then run `npx projen` to regenerate the project files. +- **Check .projenrc first**: Before suggesting changes to package.json, tsconfig.json, or other configuration files, always check if these are managed by projen and suggest changes to .projenrc instead. + +### Dependencies + +- **Add dependencies through projen**: Use the projen configuration to add dependencies instead of manually editing package.json or using npm/yarn install directly. +- **Example**: In .projenrc, use methods like `addDeps()`, `addDevDeps()`, or `addPeerDeps()` to add dependencies. + +### Workflow + +1. Make changes to .projenrc configuration file +2. Run `npx projen` to synthesize and update generated files +3. Review the changes +4. Commit both .projenrc and the generated files + +## Projen Configuration + +This project's configuration is defined in the .projenrc file at the root of the repository. All project metadata, dependencies, scripts, and tooling configuration should be managed through this file. + +## Additional Resources + +- [Projen Documentation](https://projen.io) +- [Projen GitHub Repository](https://github.com/projen/projen) + +# Development Best Practices + +- **Always run build after changes**: After modifying any source or test file, run `npx projen build` to ensure your changes compile and pass all tests. +- **Task completion criteria**: A task is not considered complete until: + - All tests pass (`npx projen test`) + - There are no compilation errors (`npx projen compile`) + - There are no linting errors (usually part of the build, if not, run the linter defined in tasks.json) + - The full build succeeds (`npx projen build`) diff --git a/CLAUDE.md b/CLAUDE.md new file mode 100644 index 0000000..efd17c8 --- /dev/null +++ b/CLAUDE.md @@ -0,0 +1,51 @@ +# Projen-managed Project Instructions + +This project is managed by [projen](https://github.com/projen/projen), a project configuration management tool. + +## Important Guidelines + +### Task Execution + +- **Always use projen for task execution**: Run tasks using `npx projen ` instead of directly using npm, yarn, or other package managers. +- **Check available tasks**: Look in `.projen/tasks.json` to see all available tasks, their descriptions, and steps. +- **Common tasks**: + - `npx projen` - Synthesize project configuration files + - `npx projen build` - Builds the project, including running tests + - `npx projen test` - Runs tests only + - `npx projen compile` - Compiles the source code only + +### File Modifications + +- **DO NOT manually edit generated files**: Files marked with a comment like "~~ Generated by projen. To modify..." should never be edited directly. +- **Modify configuration in .projenrc**: To change project configuration, always edit the `.projenrc.ts`, `.projenrc.py` or `.projenrc.json` etc. file and then run `npx projen` to regenerate the project files. +- **Check .projenrc first**: Before suggesting changes to package.json, tsconfig.json, or other configuration files, always check if these are managed by projen and suggest changes to .projenrc instead. + +### Dependencies + +- **Add dependencies through projen**: Use the projen configuration to add dependencies instead of manually editing package.json or using npm/yarn install directly. +- **Example**: In .projenrc, use methods like `addDeps()`, `addDevDeps()`, or `addPeerDeps()` to add dependencies. + +### Workflow + +1. Make changes to .projenrc configuration file +2. Run `npx projen` to synthesize and update generated files +3. Review the changes +4. Commit both .projenrc and the generated files + +## Projen Configuration + +This project's configuration is defined in the .projenrc file at the root of the repository. All project metadata, dependencies, scripts, and tooling configuration should be managed through this file. + +## Additional Resources + +- [Projen Documentation](https://projen.io) +- [Projen GitHub Repository](https://github.com/projen/projen) + +# Development Best Practices + +- **Always run build after changes**: After modifying any source or test file, run `npx projen build` to ensure your changes compile and pass all tests. +- **Task completion criteria**: A task is not considered complete until: + - All tests pass (`npx projen test`) + - There are no compilation errors (`npx projen compile`) + - There are no linting errors (usually part of the build, if not, run the linter defined in tasks.json) + - The full build succeeds (`npx projen build`) diff --git a/package.json b/package.json index a060d3e..61a28e0 100644 --- a/package.json +++ b/package.json @@ -36,7 +36,7 @@ }, "devDependencies": { "@aws-cdk/integ-tests-alpha": "^2.87.0-alpha.0", - "@time-loop/clickup-projen": "^1.23.0", + "@time-loop/clickup-projen": "^1.24.0", "@types/aws-lambda": "^8.10.152", "@types/jest": "^29.5.14", "@types/node": "^18", @@ -61,7 +61,7 @@ "jsii-rosetta": "~5.8.0", "multi-convention-namer": "0.1.15", "prettier": "^3.6.2", - "projen": "^0.98.11", + "projen": "^0.98.34", "ts-jest": "^29.4.1", "ts-node": "^10", "typescript": "~5.7.0" diff --git a/pnpm-lock.yaml b/pnpm-lock.yaml index bcd368f..f3a4975 100644 --- a/pnpm-lock.yaml +++ b/pnpm-lock.yaml @@ -25,8 +25,8 @@ importers: specifier: ^2.87.0-alpha.0 version: 2.87.0-alpha.0(aws-cdk-lib@2.87.0(constructs@10.0.5))(constructs@10.0.5) '@time-loop/clickup-projen': - specifier: ^1.23.0 - version: 1.23.0(projen@0.98.11(constructs@10.0.5)) + specifier: ^1.24.0 + version: 1.24.0(projen@0.98.34(constructs@10.0.5)) '@types/aws-lambda': specifier: ^8.10.152 version: 8.10.152 @@ -100,8 +100,8 @@ importers: specifier: ^3.6.2 version: 3.6.2 projen: - specifier: ^0.98.11 - version: 0.98.11(constructs@10.0.5) + specifier: ^0.98.34 + version: 0.98.34(constructs@10.0.5) ts-jest: specifier: ^29.4.1 version: 29.4.1(@babel/core@7.24.5)(@jest/transform@29.7.0)(@jest/types@29.6.3)(babel-jest@29.7.0(@babel/core@7.24.5))(esbuild@0.20.2)(jest-util@29.7.0)(jest@29.7.0(@types/node@18.19.33)(ts-node@10.9.2(@types/node@18.19.33)(typescript@5.7.3)))(typescript@5.7.3) @@ -1045,8 +1045,8 @@ packages: resolution: {integrity: sha512-b+zebfKCfRdgNJDknHCob3O7FpeYQN6ZG6YLExMcasDHsCXlsXCEuiPZeLnJLpwa5dvPetGlnGCiMHuLwGvFow==} engines: {node: '>=18.0.0'} - '@time-loop/clickup-projen@1.23.0': - resolution: {integrity: sha512-wqcKINGQ/zkgYfjs+Q1lWswuVXbVmFnc8c2WnAij3o1nl1Xkx2bU9ERRjqI+wk52fZtExdmJA7GzhR45yjbnlg==, tarball: https://npm.pkg.github.com/download/@time-loop/clickup-projen/1.23.0/687db9d6bdb990e9752aa2892e6cf3c9470097f0} + '@time-loop/clickup-projen@1.24.0': + resolution: {integrity: sha512-vVDBDDXpceDR1c924+J8G3KabhdHD6HpI76D581+br4BbXVxP08yL+UKE1S6UQIs+/7F1N7GdZsQRu7uFeBaDg==, tarball: https://npm.pkg.github.com/download/@time-loop/clickup-projen/1.24.0/88cf240ad326e1b7c25053b32b93acfd7e94d467} engines: {node: '>= 18.17.1'} peerDependencies: projen: ^0.98.6 @@ -3279,8 +3279,8 @@ packages: process-nextick-args@2.0.1: resolution: {integrity: sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==} - projen@0.98.11: - resolution: {integrity: sha512-4dSJFxs7rm9p0bffXjcLQ3HSRyRNpFtFDoyqxYFodxwDJXoZrDVFDAXgOqDWRTVX73bLtOSd7cZB6HPBk7QEMA==} + projen@0.98.34: + resolution: {integrity: sha512-52JX/fz5iZiy+F5r5MJjpLMtUM1sryQZVGGAVRruR6G6r8J8L/QBLXKnjss7gLPs0hbAcsCx1Zu81lh6Vnm0rA==} engines: {node: '>= 16.0.0'} hasBin: true peerDependencies: @@ -3912,6 +3912,7 @@ packages: whatwg-encoding@3.1.1: resolution: {integrity: sha512-6qN4hJdMwfYBtE3YBTTHhoeuUrDBPZmbQaxWAqSALV/MeEnR5z1xd8UKud2RAkFoPkmB+hli1TZSnyi84xz1vQ==} engines: {node: '>=18'} + deprecated: Use @exodus/bytes instead for a more spec-conformant and faster implementation whatwg-mimetype@4.0.0: resolution: {integrity: sha512-QaKxh0eNIi2mE9p2vEdzfagOKHCcj1pJ56EEHGQOVxp8r9/iszLUUV7v89x9O1p/T+NlTM5W7jW6+cz4Fq1YVg==} @@ -5471,9 +5472,9 @@ snapshots: '@smithy/util-buffer-from': 4.0.0 tslib: 2.6.2 - '@time-loop/clickup-projen@1.23.0(projen@0.98.11(constructs@10.0.5))': + '@time-loop/clickup-projen@1.24.0(projen@0.98.34(constructs@10.0.5))': dependencies: - projen: 0.98.11(constructs@10.0.5) + projen: 0.98.34(constructs@10.0.5) '@tsconfig/node10@1.0.11': {} @@ -8191,7 +8192,7 @@ snapshots: process-nextick-args@2.0.1: {} - projen@0.98.11(constructs@10.0.5): + projen@0.98.34(constructs@10.0.5): dependencies: constructs: 10.0.5 diff --git a/renovate.json5 b/renovate.json5 index 25155a8..8a46411 100644 --- a/renovate.json5 +++ b/renovate.json5 @@ -84,7 +84,6 @@ "pnpm/action-setup", "amannn/action-semantic-pull-request", "actions/setup-node", - "codecov/codecov-action", "actions/upload-artifact", "Glennmen/datadog-event-action", "rtCamp/action-slack-notify",