projen-modules 5.3.0__tar.gz → 5.4.0__tar.gz

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.
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: projen_modules
3
- Version: 5.3.0
3
+ Version: 5.4.0
4
4
  Summary: A collection of projen modules
5
5
  Home-page: https://github.com/daveshepherd/projen-modules.git
6
6
  Author: Dave Shepherd<dave.shepherd@endor.me.uk>
@@ -91,44 +91,7 @@ All source is located in `src` and is grouped by:
91
91
 
92
92
  ## GitHub Configuration
93
93
 
94
- All pull requests are merged by the [Mergify](https://mergify.com) merge queue, configured in `.mergify.yml`. Once a pull request is approved, or is opened by `daveshepherd`, and its checks pass, Mergify queues it, brings it up to date with the default branch, waits for the checks again and squash merges it. Draft pull requests and those labelled `do-not-merge` are not merged.
95
-
96
- The repository must be configured as below so that nothing can be merged without going through the queue.
97
-
98
- ### Mergify
99
-
100
- Install the [Mergify GitHub App](https://github.com/apps/mergify) and give it access to this repository.
101
-
102
- ### Pull request settings
103
-
104
- In **Settings → General → Pull Requests**:
105
-
106
- * Allow squash merging only (untick merge commits and rebase merging), matching the queue's merge method.
107
- * Untick **Allow auto-merge**, because GitHub's own auto-merge merges outside the queue.
108
- * Tick **Automatically delete head branches**.
109
-
110
- ### Actions settings
111
-
112
- In **Settings → Actions → General**, set **Approval for running fork pull request workflows from contributors** to **Require approval for all external contributors**. A pull request from a fork runs its own copy of the workflows, so it can change how the required checks pass.
113
-
114
- ### Code scanning
115
-
116
- CodeQL runs from `.github/workflows/codeql.yml`, which is managed by projen. In **Settings → Advanced Security**, leave CodeQL **Default setup** off, because it cannot run alongside this workflow. Under **Protection rules**, keep the **Check run failure threshold** at **High or higher** for security alerts and **Errors** for other alerts, as this decides whether the `CodeQL` check fails. Private repositories also need GitHub Code Security enabled there for code scanning results to be uploaded.
117
-
118
- ### Branch ruleset
119
-
120
- In **Settings → Rules → Rulesets**, create a branch ruleset with enforcement **Active** that targets the default branch, and set:
121
-
122
- * **Bypass list**: the **Mergify** app only, in **Exempt** mode. Do not add admins or other roles, as anyone on this list can merge without the queue.
123
- * **Restrict updates**: only bypass actors can update the branch, so pull requests cannot be merged from the GitHub UI or CLI and commits cannot be pushed directly.
124
- * **Restrict deletions** and **Block force pushes**.
125
- * **Require a pull request before merging**, with 0 required approvals, because Mergify requires approvals itself for authors other than `daveshepherd` and is exempt from this rule. Tick **Dismiss stale pull request approvals when new commits are pushed**, so that commits pushed after an approval need approving again before the queue merges them.
126
- * **Require status checks to pass**, listing the checks that `.mergify.yml` waits for: `build`, `package-js`, `package-python`. Leave **Require branches to be up to date before merging** unticked, as the queue already updates and retests each pull request.
127
- * **Require code scanning results**, with the tool **CodeQL**, security alerts set to **High or higher** and alerts set to **Errors**. Mergify is exempt from this rule, so `.mergify.yml` also waits for the `CodeQL` check instead.
128
-
129
- Do not enable GitHub's own **Require merge queue** rule, as it competes with Mergify.
130
-
131
- If the queue is unavailable and a change has to be merged, add yourself to the bypass list temporarily and remove yourself afterwards.
94
+ The one-off configuration that this repository needs on GitHub, such as the Mergify merge queue and the branch ruleset, is described in [docs/github-configuration.md](docs/github-configuration.md).
132
95
 
133
96
  ## Known Issues
134
97
 
@@ -0,0 +1,74 @@
1
+ <!-- ~~ Generated by projen. To modify, edit .projenrc.ts and run "npx projen". -->
2
+
3
+ # projen-modules
4
+
5
+ A collection of custom projen modules, that can be used to bootstrap and maintain consistent project configuration, tooling, dependencies, and builds.
6
+
7
+ ## Getting Started
8
+
9
+ Prerequisites:
10
+
11
+ * Node.js 22
12
+ * Yarn 1 (classic)
13
+
14
+ ```sh
15
+ yarn install
16
+ npx projen build
17
+ ```
18
+
19
+ This will:
20
+
21
+ * Install the dependencies
22
+ * Apply any projen changes
23
+ * Run tests
24
+ * Package project locally
25
+
26
+ Any files changed by projen should be committed to git.
27
+
28
+ Running the tests like this will update any snapshot files, this should be reviewed and committed to git.
29
+
30
+ ## Testing
31
+
32
+ Types of testing:
33
+
34
+ * Snapshot - projen project outputs are stored as a snapshot in the corresponding `__snapshots__` directory. When the project changes then it is expected that these snapshots change too and should be reviewed committed alongside the project.
35
+ * Unit tests - these assert on specific functionality of the project and should be written for any new functionality added.
36
+
37
+ ## Creating a New Project
38
+
39
+ ```
40
+ npx projen new {project} --from projen-modules
41
+ ```
42
+
43
+ Some projects may have required fields that need to be specified as part of this command, review any errors for details what needs to be specified.
44
+
45
+ ### Project Types
46
+
47
+ | Project type | Description |
48
+ | ---------------------------------------------- | -------------------------- |
49
+ | [cdk-typescript-app](API.md#cdktypescriptapp-) | A typescript CDK app |
50
+ | [npm-package](API.md#npmpackage-) | A typescript npm package |
51
+ | [python-package](API.md#pythonpackage-) | A python package |
52
+ | [jsii-package](API.md#jsiiproject-) | A typescript JSII package |
53
+
54
+ ## Project Structure
55
+
56
+ All source is located in `src` and is grouped by:
57
+
58
+ * `components` - these are common building blocks that can be used by projects to implement specific project functionality.
59
+ * `projects` - these are projects that can be built from this project (see #something)
60
+ * `utils` - these are helper functions that are often reused
61
+
62
+ `test` contains tests, and mirrors the `src` directory structure. Within here there are `__snapshots__` which contain snapshots of project tests (see #section).
63
+
64
+ ## GitHub Configuration
65
+
66
+ The one-off configuration that this repository needs on GitHub, such as the Mergify merge queue and the branch ruleset, is described in [docs/github-configuration.md](docs/github-configuration.md).
67
+
68
+ ## Known Issues
69
+
70
+ `cdk-typescript-app` defaults to Jest 30, which hoists `@sinonjs/fake-timers` 15 whose bundled types conflict with the `@types/sinon` used by `aws-sdk-client-mock`. Projects using `aws-sdk-client-mock` can set `compilerOptions.skipLibCheck` on the test tsconfig:
71
+
72
+ ```python
73
+ project.tryFindObjectFile('test/tsconfig.json')?.addOverride('compilerOptions.skipLibCheck', true);
74
+ ```
@@ -5,7 +5,7 @@ kwargs = json.loads(
5
5
  """
6
6
  {
7
7
  "name": "projen_modules",
8
- "version": "5.3.0",
8
+ "version": "5.4.0",
9
9
  "description": "A collection of projen modules",
10
10
  "license": "Apache-2.0",
11
11
  "url": "https://github.com/daveshepherd/projen-modules.git",
@@ -26,7 +26,7 @@ kwargs = json.loads(
26
26
  ],
27
27
  "package_data": {
28
28
  "projen_modules._jsii": [
29
- "projen-modules@5.3.0.jsii.tgz"
29
+ "projen-modules@5.4.0.jsii.tgz"
30
30
  ],
31
31
  "projen_modules": [
32
32
  "py.typed"
@@ -64,44 +64,7 @@ All source is located in `src` and is grouped by:
64
64
 
65
65
  ## GitHub Configuration
66
66
 
67
- All pull requests are merged by the [Mergify](https://mergify.com) merge queue, configured in `.mergify.yml`. Once a pull request is approved, or is opened by `daveshepherd`, and its checks pass, Mergify queues it, brings it up to date with the default branch, waits for the checks again and squash merges it. Draft pull requests and those labelled `do-not-merge` are not merged.
68
-
69
- The repository must be configured as below so that nothing can be merged without going through the queue.
70
-
71
- ### Mergify
72
-
73
- Install the [Mergify GitHub App](https://github.com/apps/mergify) and give it access to this repository.
74
-
75
- ### Pull request settings
76
-
77
- In **Settings → General → Pull Requests**:
78
-
79
- * Allow squash merging only (untick merge commits and rebase merging), matching the queue's merge method.
80
- * Untick **Allow auto-merge**, because GitHub's own auto-merge merges outside the queue.
81
- * Tick **Automatically delete head branches**.
82
-
83
- ### Actions settings
84
-
85
- In **Settings → Actions → General**, set **Approval for running fork pull request workflows from contributors** to **Require approval for all external contributors**. A pull request from a fork runs its own copy of the workflows, so it can change how the required checks pass.
86
-
87
- ### Code scanning
88
-
89
- CodeQL runs from `.github/workflows/codeql.yml`, which is managed by projen. In **Settings → Advanced Security**, leave CodeQL **Default setup** off, because it cannot run alongside this workflow. Under **Protection rules**, keep the **Check run failure threshold** at **High or higher** for security alerts and **Errors** for other alerts, as this decides whether the `CodeQL` check fails. Private repositories also need GitHub Code Security enabled there for code scanning results to be uploaded.
90
-
91
- ### Branch ruleset
92
-
93
- In **Settings → Rules → Rulesets**, create a branch ruleset with enforcement **Active** that targets the default branch, and set:
94
-
95
- * **Bypass list**: the **Mergify** app only, in **Exempt** mode. Do not add admins or other roles, as anyone on this list can merge without the queue.
96
- * **Restrict updates**: only bypass actors can update the branch, so pull requests cannot be merged from the GitHub UI or CLI and commits cannot be pushed directly.
97
- * **Restrict deletions** and **Block force pushes**.
98
- * **Require a pull request before merging**, with 0 required approvals, because Mergify requires approvals itself for authors other than `daveshepherd` and is exempt from this rule. Tick **Dismiss stale pull request approvals when new commits are pushed**, so that commits pushed after an approval need approving again before the queue merges them.
99
- * **Require status checks to pass**, listing the checks that `.mergify.yml` waits for: `build`, `package-js`, `package-python`. Leave **Require branches to be up to date before merging** unticked, as the queue already updates and retests each pull request.
100
- * **Require code scanning results**, with the tool **CodeQL**, security alerts set to **High or higher** and alerts set to **Errors**. Mergify is exempt from this rule, so `.mergify.yml` also waits for the `CodeQL` check instead.
101
-
102
- Do not enable GitHub's own **Require merge queue** rule, as it competes with Mergify.
103
-
104
- If the queue is unavailable and a change has to be merged, add yourself to the bypass list temporarily and remove yourself afterwards.
67
+ The one-off configuration that this repository needs on GitHub, such as the Mergify merge queue and the branch ruleset, is described in [docs/github-configuration.md](docs/github-configuration.md).
105
68
 
106
69
  ## Known Issues
107
70
 
@@ -18,7 +18,7 @@ import constructs._jsii
18
18
  import projen._jsii
19
19
 
20
20
  __jsii_assembly__ = jsii.JSIIAssembly.load(
21
- "projen-modules", "5.3.0", __name__[0:-6], "projen-modules@5.3.0.jsii.tgz"
21
+ "projen-modules", "5.4.0", __name__[0:-6], "projen-modules@5.4.0.jsii.tgz"
22
22
  )
23
23
 
24
24
  __all__ = [
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.1
2
2
  Name: projen_modules
3
- Version: 5.3.0
3
+ Version: 5.4.0
4
4
  Summary: A collection of projen modules
5
5
  Home-page: https://github.com/daveshepherd/projen-modules.git
6
6
  Author: Dave Shepherd<dave.shepherd@endor.me.uk>
@@ -91,44 +91,7 @@ All source is located in `src` and is grouped by:
91
91
 
92
92
  ## GitHub Configuration
93
93
 
94
- All pull requests are merged by the [Mergify](https://mergify.com) merge queue, configured in `.mergify.yml`. Once a pull request is approved, or is opened by `daveshepherd`, and its checks pass, Mergify queues it, brings it up to date with the default branch, waits for the checks again and squash merges it. Draft pull requests and those labelled `do-not-merge` are not merged.
95
-
96
- The repository must be configured as below so that nothing can be merged without going through the queue.
97
-
98
- ### Mergify
99
-
100
- Install the [Mergify GitHub App](https://github.com/apps/mergify) and give it access to this repository.
101
-
102
- ### Pull request settings
103
-
104
- In **Settings → General → Pull Requests**:
105
-
106
- * Allow squash merging only (untick merge commits and rebase merging), matching the queue's merge method.
107
- * Untick **Allow auto-merge**, because GitHub's own auto-merge merges outside the queue.
108
- * Tick **Automatically delete head branches**.
109
-
110
- ### Actions settings
111
-
112
- In **Settings → Actions → General**, set **Approval for running fork pull request workflows from contributors** to **Require approval for all external contributors**. A pull request from a fork runs its own copy of the workflows, so it can change how the required checks pass.
113
-
114
- ### Code scanning
115
-
116
- CodeQL runs from `.github/workflows/codeql.yml`, which is managed by projen. In **Settings → Advanced Security**, leave CodeQL **Default setup** off, because it cannot run alongside this workflow. Under **Protection rules**, keep the **Check run failure threshold** at **High or higher** for security alerts and **Errors** for other alerts, as this decides whether the `CodeQL` check fails. Private repositories also need GitHub Code Security enabled there for code scanning results to be uploaded.
117
-
118
- ### Branch ruleset
119
-
120
- In **Settings → Rules → Rulesets**, create a branch ruleset with enforcement **Active** that targets the default branch, and set:
121
-
122
- * **Bypass list**: the **Mergify** app only, in **Exempt** mode. Do not add admins or other roles, as anyone on this list can merge without the queue.
123
- * **Restrict updates**: only bypass actors can update the branch, so pull requests cannot be merged from the GitHub UI or CLI and commits cannot be pushed directly.
124
- * **Restrict deletions** and **Block force pushes**.
125
- * **Require a pull request before merging**, with 0 required approvals, because Mergify requires approvals itself for authors other than `daveshepherd` and is exempt from this rule. Tick **Dismiss stale pull request approvals when new commits are pushed**, so that commits pushed after an approval need approving again before the queue merges them.
126
- * **Require status checks to pass**, listing the checks that `.mergify.yml` waits for: `build`, `package-js`, `package-python`. Leave **Require branches to be up to date before merging** unticked, as the queue already updates and retests each pull request.
127
- * **Require code scanning results**, with the tool **CodeQL**, security alerts set to **High or higher** and alerts set to **Errors**. Mergify is exempt from this rule, so `.mergify.yml` also waits for the `CodeQL` check instead.
128
-
129
- Do not enable GitHub's own **Require merge queue** rule, as it competes with Mergify.
130
-
131
- If the queue is unavailable and a change has to be merged, add yourself to the bypass list temporarily and remove yourself afterwards.
94
+ The one-off configuration that this repository needs on GitHub, such as the Mergify merge queue and the branch ruleset, is described in [docs/github-configuration.md](docs/github-configuration.md).
132
95
 
133
96
  ## Known Issues
134
97
 
@@ -11,4 +11,4 @@ src/projen_modules.egg-info/dependency_links.txt
11
11
  src/projen_modules.egg-info/requires.txt
12
12
  src/projen_modules.egg-info/top_level.txt
13
13
  src/projen_modules/_jsii/__init__.py
14
- src/projen_modules/_jsii/projen-modules@5.3.0.jsii.tgz
14
+ src/projen_modules/_jsii/projen-modules@5.4.0.jsii.tgz
@@ -1,111 +0,0 @@
1
- <!-- ~~ Generated by projen. To modify, edit .projenrc.ts and run "npx projen". -->
2
-
3
- # projen-modules
4
-
5
- A collection of custom projen modules, that can be used to bootstrap and maintain consistent project configuration, tooling, dependencies, and builds.
6
-
7
- ## Getting Started
8
-
9
- Prerequisites:
10
-
11
- * Node.js 22
12
- * Yarn 1 (classic)
13
-
14
- ```sh
15
- yarn install
16
- npx projen build
17
- ```
18
-
19
- This will:
20
-
21
- * Install the dependencies
22
- * Apply any projen changes
23
- * Run tests
24
- * Package project locally
25
-
26
- Any files changed by projen should be committed to git.
27
-
28
- Running the tests like this will update any snapshot files, this should be reviewed and committed to git.
29
-
30
- ## Testing
31
-
32
- Types of testing:
33
-
34
- * Snapshot - projen project outputs are stored as a snapshot in the corresponding `__snapshots__` directory. When the project changes then it is expected that these snapshots change too and should be reviewed committed alongside the project.
35
- * Unit tests - these assert on specific functionality of the project and should be written for any new functionality added.
36
-
37
- ## Creating a New Project
38
-
39
- ```
40
- npx projen new {project} --from projen-modules
41
- ```
42
-
43
- Some projects may have required fields that need to be specified as part of this command, review any errors for details what needs to be specified.
44
-
45
- ### Project Types
46
-
47
- | Project type | Description |
48
- | ---------------------------------------------- | -------------------------- |
49
- | [cdk-typescript-app](API.md#cdktypescriptapp-) | A typescript CDK app |
50
- | [npm-package](API.md#npmpackage-) | A typescript npm package |
51
- | [python-package](API.md#pythonpackage-) | A python package |
52
- | [jsii-package](API.md#jsiiproject-) | A typescript JSII package |
53
-
54
- ## Project Structure
55
-
56
- All source is located in `src` and is grouped by:
57
-
58
- * `components` - these are common building blocks that can be used by projects to implement specific project functionality.
59
- * `projects` - these are projects that can be built from this project (see #something)
60
- * `utils` - these are helper functions that are often reused
61
-
62
- `test` contains tests, and mirrors the `src` directory structure. Within here there are `__snapshots__` which contain snapshots of project tests (see #section).
63
-
64
- ## GitHub Configuration
65
-
66
- All pull requests are merged by the [Mergify](https://mergify.com) merge queue, configured in `.mergify.yml`. Once a pull request is approved, or is opened by `daveshepherd`, and its checks pass, Mergify queues it, brings it up to date with the default branch, waits for the checks again and squash merges it. Draft pull requests and those labelled `do-not-merge` are not merged.
67
-
68
- The repository must be configured as below so that nothing can be merged without going through the queue.
69
-
70
- ### Mergify
71
-
72
- Install the [Mergify GitHub App](https://github.com/apps/mergify) and give it access to this repository.
73
-
74
- ### Pull request settings
75
-
76
- In **Settings → General → Pull Requests**:
77
-
78
- * Allow squash merging only (untick merge commits and rebase merging), matching the queue's merge method.
79
- * Untick **Allow auto-merge**, because GitHub's own auto-merge merges outside the queue.
80
- * Tick **Automatically delete head branches**.
81
-
82
- ### Actions settings
83
-
84
- In **Settings → Actions → General**, set **Approval for running fork pull request workflows from contributors** to **Require approval for all external contributors**. A pull request from a fork runs its own copy of the workflows, so it can change how the required checks pass.
85
-
86
- ### Code scanning
87
-
88
- CodeQL runs from `.github/workflows/codeql.yml`, which is managed by projen. In **Settings → Advanced Security**, leave CodeQL **Default setup** off, because it cannot run alongside this workflow. Under **Protection rules**, keep the **Check run failure threshold** at **High or higher** for security alerts and **Errors** for other alerts, as this decides whether the `CodeQL` check fails. Private repositories also need GitHub Code Security enabled there for code scanning results to be uploaded.
89
-
90
- ### Branch ruleset
91
-
92
- In **Settings → Rules → Rulesets**, create a branch ruleset with enforcement **Active** that targets the default branch, and set:
93
-
94
- * **Bypass list**: the **Mergify** app only, in **Exempt** mode. Do not add admins or other roles, as anyone on this list can merge without the queue.
95
- * **Restrict updates**: only bypass actors can update the branch, so pull requests cannot be merged from the GitHub UI or CLI and commits cannot be pushed directly.
96
- * **Restrict deletions** and **Block force pushes**.
97
- * **Require a pull request before merging**, with 0 required approvals, because Mergify requires approvals itself for authors other than `daveshepherd` and is exempt from this rule. Tick **Dismiss stale pull request approvals when new commits are pushed**, so that commits pushed after an approval need approving again before the queue merges them.
98
- * **Require status checks to pass**, listing the checks that `.mergify.yml` waits for: `build`, `package-js`, `package-python`. Leave **Require branches to be up to date before merging** unticked, as the queue already updates and retests each pull request.
99
- * **Require code scanning results**, with the tool **CodeQL**, security alerts set to **High or higher** and alerts set to **Errors**. Mergify is exempt from this rule, so `.mergify.yml` also waits for the `CodeQL` check instead.
100
-
101
- Do not enable GitHub's own **Require merge queue** rule, as it competes with Mergify.
102
-
103
- If the queue is unavailable and a change has to be merged, add yourself to the bypass list temporarily and remove yourself afterwards.
104
-
105
- ## Known Issues
106
-
107
- `cdk-typescript-app` defaults to Jest 30, which hoists `@sinonjs/fake-timers` 15 whose bundled types conflict with the `@types/sinon` used by `aws-sdk-client-mock`. Projects using `aws-sdk-client-mock` can set `compilerOptions.skipLibCheck` on the test tsconfig:
108
-
109
- ```python
110
- project.tryFindObjectFile('test/tsconfig.json')?.addOverride('compilerOptions.skipLibCheck', true);
111
- ```
File without changes
File without changes