chore(release): 1.119.0 (#4979)

See [CHANGELOG](https://github.com/aws/jsii/blob/bump/1.119.0/CHANGELOG.md)

Author: mergify[bot]

CHANGELOG.md

@@ -2,6 +2,20 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+## [1.119.0](https://github.com/aws/jsii/compare/v1.118.0...v1.119.0) (2025-11-10)
+
+
+### Features
+
+* **jsii-diff:** remap old to new FQNs ([#4976](https://github.com/aws/jsii/issues/4976)) ([d7c083d](https://github.com/aws/jsii/commit/d7c083d9a958ddb6205ae0237d032c818668d471))
+* **jsii-reflect:** can jqii-query on `fqn` field ([#4975](https://github.com/aws/jsii/issues/4975)) ([86995e5](https://github.com/aws/jsii/commit/86995e544528d19f91631e7acff1d744a2383ae1))
+
+
+### Bug Fixes
+
+* **jsii-pacmak:** Python interfaces sometimes violate MRO ([#4973](https://github.com/aws/jsii/issues/4973)) ([cfb6580](https://github.com/aws/jsii/commit/cfb658077b8f3f7e464a50f5d17f5594a77e9029))
+* **jsii-reflect:** advertise `jsii-query` via `bin` entry of `package.json` ([#4974](https://github.com/aws/jsii/issues/4974)) ([b6c0a35](https://github.com/aws/jsii/commit/b6c0a3511705bc6e021ce23ea1d480552a7cdfaa))
+
 ## [1.118.0](https://github.com/aws/jsii/compare/v1.117.0...v1.118.0) (2025-10-29)
 
 

gh-pages/content/user-guides/lib-author/configuration/targets/.pages.yml

@@ -5,3 +5,4 @@ nav:
   - Go: go.md
   - Java: java.md
   - Python: python.md
+  - Submodules: submodules.md

gh-pages/content/user-guides/lib-author/configuration/targets/submodules.md

@@ -0,0 +1,110 @@
+# Submodules
+
+jsii allows the use of submodules. These make it possible for classes with the
+same name to live in different namespaces in the jsii type system, so that they
+don't conflict.
+
+For example, "cluster" is a very popular name; in the AWS ecosystem RDS has
+Clusters, ECS has Clusters, EKS has Clusters, and so on. We want multiple
+classes named `Cluster` in a single code library, but in order to make sure
+the names don't conflict, every class is placed in a different submodule.
+
+## Defining submodules
+
+A submodule is declared by using an aliased TypeScript `export *` statement, in
+any file reachable from the library's entry point, in the following form:
+
+```ts
+export * as my_module from `./my-module`;
+//            ^^^               ^^^
+//     Submodule name       Submodule source
+```
+
+All types reachable from `./my-module` will be in the submodule named
+`my_module.` `./my-module` can either point directly to a source file, or to a
+directory with an `index.ts` file in it.
+
+A TypeScript *consumer* accesses the classes inside the submodule by importing
+the submodule symbol from the library's entry point and then accessing
+properties off of that, OR by importing the target file directly:
+
+```ts
+// Normal access via library entry point
+import { my_module } from '@my-jsii/library';
+new my_module.ClassInSubmodule(...);
+
+// -------------------------------------------------------------------------
+// Direct access of source file
+
+// This is outside of the purview of jsii and is subject to the files that
+// are being declared `export`ed in your `package.json`.
+import { ClassInSubmodule } from '@my-jsii/library/my-module';
+new ClassInSubmodule(...);
+```
+
+Consumers in jsii client languages use a regular namespaced import:
+
+```py
+from my_jsii_library.my_module import ClassInModule
+```
+
+```java
+import com.library.jsii.my.my_module.ClassInmodule;
+```
+
+...etc.
+
+## Configuring submodule attributes
+
+If unconfigured, a namespace name will automatically be derived by `jsii-pacmak`
+based on the exported name of the submodule. If you want to explicitly configure
+the namespace you can put a `.jsiirc.json` file in the right location:
+
+If your submodule export is a `directory/index.ts`, place a `.jsiirc.json` file
+in the directory:
+
+```js
+/*
+.
+├── index.ts
+├── package.json          // <- namespaces for the library root here
+└── my-submodule
+    ├── .jsiirc.json      // <- namespaces for the submodule here
+    └── index.ts
+*/
+
+{
+  "targets": {
+    "java": {
+      "package": "com.my_company.my_jsii_library.fancy_submodule"
+    },
+    "dotnet": {
+      "namespace": "MyCompany.MyJsiiLibrary.FancySubmodule"
+    },
+    "python": {
+      "module": "my_jsii_library.fancy_submodule"
+    },
+    "go": {
+      "packageName": "fancy_submodule"
+    }
+  }
+}
+```
+
+If your submodule export is a file, name your rc-file `.<base-name>.jsiirc.json`:
+
+```js
+/*
+.
+├── index.ts
+├── package.json               // <- namespaces for the library root here
+├── my-submodule.ts
+└── .my-submodule.jsiirc.json  // <- namespaces for the submodule here
+*/
+
+{
+  "targets": {
+    /* ... */
+  }
+}
+```

gh-pages/requirements-dev.txt

@@ -1,4 +1,4 @@
 mkdocs~=1.6.1
 mkdocs-awesome-pages-plugin~=2.10.1
-mkdocs-material~=9.6.22
+mkdocs-material~=9.6.23
 mkdocs-git-revision-date-plugin~=0.3.2

lerna.json

@@ -12,6 +12,6 @@
       "rejectCycles": true
     }
   },
-  "version": "1.118.0",
+  "version": "1.119.0",
   "$schema": "node_modules/lerna/schemas/lerna-schema.json"
 }

packages/@jsii/python-runtime/requirements.txt

@@ -1,4 +1,4 @@
-black~=25.9
+black~=25.11
 mypy==1.18.2
 pip~=25.3
 pytest~=8.4

packages/jsii-diff/README.md

@@ -126,6 +126,45 @@ abstract members yet.
 for subclassing, but treating them as such would limit the evolvability of
 libraries too much.
 
+## Accepting breaking changes
+
+Sometimes you want to move forward with a change, even if it would technically
+be a breaking change to your API. In order to do that, run `jsii-diff`
+with the flag `--keys`. It will then print an identifier for every violation
+between square brackets, for example:
+
+```
+$ jsii-diff <old> --keys
+IFACE pkg.MyStruct: formerly required property 'prop' is optional: returned from pkg.IConsumer.someMethod [weakened:pkg.MyStruct]
+```
+
+To accept a breaking finding, put the key (in this example `weakened:pkg.MyStruct`)
+into a text file, for example `allowed-breaking-changes.txt`, and pass it to
+`jsii-diff` as an ignore file:
+
+```
+$ jsii-diff <old> --keys --ignore-file allowed-breaking-changes.txt
+(no error)
+```
+
+### Moving/renaming API elements
+
+If you've moved API elements around between versions of your library, you can
+put a special ignore marker starting with `move:` into your `--ignore-file`.  To
+separate the old and new class names, you can use `:`, `,` or whitespace.
+
+For example:
+
+```
+move:package.OldClassName    package.NewClassName
+move:package.OldClassName:package.NewClassName
+move:package.OldClassName, package.NewClassName
+```
+
+Moving API elements is always breaking, but using this feature you can confirm
+that you at least didn't break anything in the API surface of the moved classes
+themselves.
+
 ## Help! jsii-diff is marking my changes as breaking
 
 See [BREAKING_CHANGES.md](./BREAKING_CHANGES.md) for more information.

packages/jsii-diff/bin/jsii-diff.ts

@@ -124,9 +124,15 @@ async function main(): Promise<number> {
     );
   }
 
+  const allowedBreakingChanges = await loadFilter(argv['ignore-file']);
+  const fqnRemapping: Record<string, string> = extractFqnRemappings(
+    allowedBreakingChanges,
+  );
+
   LOG.info('Starting analysis');
   const mismatches = compareAssemblies(original, updated, {
     defaultExperimental: argv['default-stability'] === 'experimental',
+    fqnRemapping,
   });
 
   LOG.info(`Found ${mismatches.count} issues`);
@@ -135,7 +141,7 @@ async function main(): Promise<number> {
     const diags = classifyDiagnostics(
       mismatches,
       treatAsError(argv['error-on'] as ErrorClass, argv['experimental-errors']),
-      await loadFilter(argv['ignore-file']),
+      allowedBreakingChanges,
     );
 
     process.stderr.write(
@@ -155,6 +161,43 @@ async function main(): Promise<number> {
   return 0;
 }
 
+/**
+ * Extract all lines that start with `move:` from the given string set
+ *
+ * Interpret them as `move:OLDFQN <sep> NEWFQN`, mapping moved FQNs.
+ *
+ * Separator can be any of `:`, comma or whitespace.
+ *
+ * Modifies the input set in-place.
+ */
+function extractFqnRemappings(
+  allowedBreakingChanges: Set<string>,
+): Record<string, string> {
+  const ret: Record<string, string> = {};
+
+  for (const line of Array.from(allowedBreakingChanges)) {
+    const prefix = 'move:';
+    if (!line.startsWith(prefix)) {
+      continue;
+    }
+
+    const parts = line
+      .slice(prefix.length)
+      .trim()
+      .split(/[:, \t]+/g);
+    if (parts.length !== 2) {
+      throw new Error(
+        `Invalid moved FQN declaration: ${line}. Expected format is 'move:old:new'`,
+      );
+    }
+    const [oldFqn, newFqn] = parts;
+    ret[oldFqn] = newFqn;
+    allowedBreakingChanges.delete(line);
+  }
+
+  return ret;
+}
+
 // Allow both npm:<package> (legacy) and npm://<package> (looks better)
 const NPM_REGEX = /^npm:(\/\/)?/;
 
@@ -311,7 +354,7 @@ async function loadFilter(filterFilename?: string): Promise<Set<string>> {
       (await fs.readFile(filterFilename, { encoding: 'utf-8' }))
         .split('\n')
         .map((x) => x.trim())
-        .filter((x) => !x.startsWith('#')),
+        .filter((x) => x && !x.startsWith('#')),
     );
   } catch (e: any) {
     if (e.code !== 'ENOENT') {