Comparing changes

This is a major re-organization of the stack refactoring code. The core change was the introduction of the `RefactoringContext`, that encapsulates the data and operations needed for a refactor, for a single environment. In future changes, this class will also start exposing methods to execute the refactor. No behavior was changed, except in the presentation layer: before, all mappings were grouped in a single table. Now, there is a section for each environment, with its own table, to make it clearer to the user that each one is a different refactor operation: ![Screenshot 2025-05-30 at 11 02 25](https://github.com/user-attachments/assets/d4ac65e6-7d7c-4e3e-9438-a5973b27e572) --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

…ng stack template (#558) Now because `getStack` is deprecated. I replaced `getStack` by `getStackByName`. --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

--- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license --------- Signed-off-by: github-actions <github-actions@github.com> Co-authored-by: github-actions <github-actions@github.com>

Upgrades project dependencies. See details in [workflow run]. [Workflow Run]: https://github.com/aws/aws-cdk-cli/actions/runs/15381104645 ------ *Automatically created by projen via the "upgrade" workflow* --------- Signed-off-by: github-actions <github-actions@github.com> Co-authored-by: github-actions <github-actions@github.com>

This introduces the concept of unstable featues to the toolkit. The CLI always opts into it because it has its own similar flag. Over time, the type `UnstableFeature` will change according to the features that are unstable at the moment. All commands that are considered unstable should call the `requireUnstableFeature` method. --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

…al exclusive options in the refactor API (#559) Introduce a new type, `MappingSource`, that allows the user to tell how they want the toolkit to get the mappings: computing it, using an explicitly provided one, or using the reverse of an explicitly provided one. This replaces three previous separate properties: `exclude`, `mappings` and `revert` with a single `mappingSource`. --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license --------- Signed-off-by: github-actions <github-actions@github.com> Co-authored-by: github-actions <github-actions@github.com>

Since May 30th, 2025, these versions are [no longer supported](https://aws.amazon.com/blogs/devops/announcing-the-end-of-support-for-node-js-14-x-and-16-x-in-aws-cdk/). --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

There should be a linter rule against this but I don't have time to write it. Without the extra `*` the documentation does not become part of the docstring for the property. --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

…tely (#567) Previously the `CloudWatchLogEventMonitor` wasn't closed immediately when the `FileWatcher` returned from `watch()` was disposed. This wasn't super bad, since it would only wait for one additional tick to finish, but also isn't great. This was discovered by jest reporting open handles. Well done jest! --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

…ing `include` or `exclude` patterns (#564) This PR improves the watch action implementation in the toolkit-lib package by: ## Changes - When neither `include` or `exclude` are been provided, the action now doesn't fail anymore. Instead sensible defaults are used. - `exclude` now uses a list of default excludes as fallback. These defaults aim to cover common development patterns for all CDK languages. - `node_modules` is no longer forcibly excluded, but part of the exclude defaults instead. This is still the behavior in the CLI but seems overly unexpected to users, especially to toolkit-lib users. We now only force exclude hidden files. ## Why these changes address the issue Previously, the watch action would throw an error if no include/exclude patterns were specified, requiring users to always configure these settings. This change makes the watch action more user-friendly by: 1. Using sensible defaults that work out-of-the-box 2. Providing better exclusion patterns for common non-source files 3. Following the principle of least surprise by watching all files by default ## Design decisions - Created a reusable constant that can be used in other parts of the codebase - Improved code comments to better explain the behavior - Maintained backward compatibility while enhancing usability - Organized exclude patterns by language/ecosystem for better maintainability ## Alternatives considered - Keeping the error but providing more guidance - rejected because a sensible default is more user-friendly - Using a more complex configuration system - rejected in favor of simplicity - Language-specific exclude patterns - kept generic to work across all supported CDK languages --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

…#569) --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license --------- Signed-off-by: github-actions <github-actions@github.com> Co-authored-by: github-actions <github-actions@github.com>

Updates the projen configuration to include the assets directory in the documentation build process. The changes: 1. Adds a step to copy files from the assets directory to the documentation output 2. Updates the docs task in .projen/tasks.json to include this new step This ensures that any assets (like images or other resources) used in the documentation are properly included in the final documentation package. --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

) API Extractor wants that, so we might as well have it everywhere. I just added the rule, fixes are automatically done by eslint. --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Just noticed some missed opportunities in the error handling for the CCAPI provider. This only has limited end-user impact: - instead of `error: cause` it's now `error\ncause` - Some not enough results found error messages now include the expectation --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

`CliAction` type feels slightly off as it should be `CliAction` and not `ToolkitAction`. This makes the default make sense. Either way, the internal property of `CliIoHost` is typed to `CliAction`. In practice this probably doesn't matter because I don't think we are initializing `CliIoHost` with anything but `none`. --- By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license --------- Co-authored-by: Momo Kornher <kornherm@amazon.co.uk>

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Comparing changes

Open a pull request

Commits on May 30, 2025

Commits on May 31, 2025

Commits on Jun 2, 2025

Commits on Jun 3, 2025

Commits on Jun 4, 2025

This comparison is taking too long to generate.

Uh oh!