azdo-release-env 1.0.0 → 1.0.1
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.
- package/.github/workflows/npm-publish.yml +34 -33
- package/CODE_OF_CONDUCT.md +92 -0
- package/CONTRIBUTING.md +137 -0
- package/README.md +3 -12
- package/package.json +39 -39
|
@@ -1,33 +1,34 @@
|
|
|
1
|
-
# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
|
|
2
|
-
# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages
|
|
3
|
-
|
|
4
|
-
name: Node.js Package
|
|
5
|
-
|
|
6
|
-
on:
|
|
7
|
-
release:
|
|
8
|
-
types: [created]
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
1
|
+
# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
|
|
2
|
+
# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages
|
|
3
|
+
|
|
4
|
+
name: Node.js Package
|
|
5
|
+
|
|
6
|
+
on:
|
|
7
|
+
release:
|
|
8
|
+
types: [created]
|
|
9
|
+
permissions:
|
|
10
|
+
id-token: write # Required for OIDC
|
|
11
|
+
contents: read
|
|
12
|
+
|
|
13
|
+
jobs:
|
|
14
|
+
build:
|
|
15
|
+
runs-on: ubuntu-latest
|
|
16
|
+
steps:
|
|
17
|
+
- uses: actions/checkout@v4
|
|
18
|
+
- uses: actions/setup-node@v4
|
|
19
|
+
with:
|
|
20
|
+
node-version: 20
|
|
21
|
+
- run: npm ci
|
|
22
|
+
- run: npm test
|
|
23
|
+
|
|
24
|
+
publish-npm:
|
|
25
|
+
needs: build
|
|
26
|
+
runs-on: ubuntu-latest
|
|
27
|
+
steps:
|
|
28
|
+
- uses: actions/checkout@v4
|
|
29
|
+
- uses: actions/setup-node@v4
|
|
30
|
+
with:
|
|
31
|
+
node-version: 20
|
|
32
|
+
registry-url: https://registry.npmjs.org/
|
|
33
|
+
- run: npm ci
|
|
34
|
+
- run: npm publish
|
|
@@ -0,0 +1,92 @@
|
|
|
1
|
+
|
|
2
|
+
# Contributor Covenant 3.0 Code of Conduct
|
|
3
|
+
|
|
4
|
+
## Our Pledge
|
|
5
|
+
|
|
6
|
+
We pledge to make our community welcoming, safe, and equitable for all.
|
|
7
|
+
|
|
8
|
+
We are committed to fostering an environment that respects and promotes the dignity, rights, and contributions of all individuals, regardless of characteristics including race, ethnicity, caste, color, age, physical characteristics, neurodiversity, disability, sex or gender, gender identity or expression, sexual orientation, language, philosophy or religion, national or social origin, socio-economic position, level of education, or other status. The same privileges of participation are extended to everyone who participates in good faith and in accordance with this Covenant.
|
|
9
|
+
|
|
10
|
+
## Encouraged Behaviors
|
|
11
|
+
|
|
12
|
+
While acknowledging differences in social norms, we all strive to meet our community's expectations for positive behavior. We also understand that our words and actions may be interpreted differently than we intend based on culture, background, or native language.
|
|
13
|
+
|
|
14
|
+
With these considerations in mind, we agree to behave mindfully toward each other and act in ways that center our shared values, including:
|
|
15
|
+
|
|
16
|
+
1. Respecting the **purpose of our community**, our activities, and our ways of gathering.
|
|
17
|
+
2. Engaging **kindly and honestly** with others.
|
|
18
|
+
3. Respecting **different viewpoints** and experiences.
|
|
19
|
+
4. **Taking responsibility** for our actions and contributions.
|
|
20
|
+
5. Gracefully giving and accepting **constructive feedback**.
|
|
21
|
+
6. Committing to **repairing harm** when it occurs.
|
|
22
|
+
7. Behaving in other ways that promote and sustain the **well-being of our community**.
|
|
23
|
+
|
|
24
|
+
|
|
25
|
+
## Restricted Behaviors
|
|
26
|
+
|
|
27
|
+
We agree to restrict the following behaviors in our community. Instances, threats, and promotion of these behaviors are violations of this Code of Conduct.
|
|
28
|
+
|
|
29
|
+
1. **Harassment.** Violating explicitly expressed boundaries or engaging in unnecessary personal attention after any clear request to stop.
|
|
30
|
+
2. **Character attacks.** Making insulting, demeaning, or pejorative comments directed at a community member or group of people.
|
|
31
|
+
3. **Stereotyping or discrimination.** Characterizing anyone’s personality or behavior on the basis of immutable identities or traits.
|
|
32
|
+
4. **Sexualization.** Behaving in a way that would generally be considered inappropriately intimate in the context or purpose of the community.
|
|
33
|
+
5. **Violating confidentiality**. Sharing or acting on someone's personal or private information without their permission.
|
|
34
|
+
6. **Endangerment.** Causing, encouraging, or threatening violence or other harm toward any person or group.
|
|
35
|
+
7. Behaving in other ways that **threaten the well-being** of our community.
|
|
36
|
+
|
|
37
|
+
### Other Restrictions
|
|
38
|
+
|
|
39
|
+
1. **Misleading identity.** Impersonating someone else for any reason, or pretending to be someone else to evade enforcement actions.
|
|
40
|
+
2. **Failing to credit sources.** Not properly crediting the sources of content you contribute.
|
|
41
|
+
3. **Promotional materials**. Sharing marketing or other commercial content in a way that is outside the norms of the community.
|
|
42
|
+
4. **Irresponsible communication.** Failing to responsibly present content which includes, links or describes any other restricted behaviors.
|
|
43
|
+
|
|
44
|
+
|
|
45
|
+
## Reporting an Issue
|
|
46
|
+
|
|
47
|
+
Tensions can occur between community members even when they are trying their best to collaborate. Not every conflict represents a code of conduct violation, and this Code of Conduct reinforces encouraged behaviors and norms that can help avoid conflicts and minimize harm.
|
|
48
|
+
|
|
49
|
+
When an incident does occur, it is important to report it promptly.
|
|
50
|
+
|
|
51
|
+
Community Moderators take reports of violations seriously and will make every effort to respond in a timely manner. They will investigate all reports of code of conduct violations, reviewing messages, logs, and recordings, or interviewing witnesses and other participants. Community Moderators will keep investigation and enforcement actions as transparent as possible while prioritizing safety and confidentiality. In order to honor these values, enforcement actions are carried out in private with the involved parties, but communicating to the whole community may be part of a mutually agreed upon resolution.
|
|
52
|
+
|
|
53
|
+
|
|
54
|
+
## Addressing and Repairing Harm
|
|
55
|
+
|
|
56
|
+
****
|
|
57
|
+
|
|
58
|
+
If an investigation by the Community Moderators finds that this Code of Conduct has been violated, the following enforcement ladder may be used to determine how best to repair harm, based on the incident's impact on the individuals involved and the community as a whole. Depending on the severity of a violation, lower rungs on the ladder may be skipped.
|
|
59
|
+
|
|
60
|
+
1) Warning
|
|
61
|
+
1) Event: A violation involving a single incident or series of incidents.
|
|
62
|
+
2) Consequence: A private, written warning from the Community Moderators.
|
|
63
|
+
3) Repair: Examples of repair include a private written apology, acknowledgement of responsibility, and seeking clarification on expectations.
|
|
64
|
+
2) Temporarily Limited Activities
|
|
65
|
+
1) Event: A repeated incidence of a violation that previously resulted in a warning, or the first incidence of a more serious violation.
|
|
66
|
+
2) Consequence: A private, written warning with a time-limited cooldown period designed to underscore the seriousness of the situation and give the community members involved time to process the incident. The cooldown period may be limited to particular communication channels or interactions with particular community members.
|
|
67
|
+
3) Repair: Examples of repair may include making an apology, using the cooldown period to reflect on actions and impact, and being thoughtful about re-entering community spaces after the period is over.
|
|
68
|
+
3) Temporary Suspension
|
|
69
|
+
1) Event: A pattern of repeated violation which the Community Moderators have tried to address with warnings, or a single serious violation.
|
|
70
|
+
2) Consequence: A private written warning with conditions for return from suspension. In general, temporary suspensions give the person being suspended time to reflect upon their behavior and possible corrective actions.
|
|
71
|
+
3) Repair: Examples of repair include respecting the spirit of the suspension, meeting the specified conditions for return, and being thoughtful about how to reintegrate with the community when the suspension is lifted.
|
|
72
|
+
4) Permanent Ban
|
|
73
|
+
1) Event: A pattern of repeated code of conduct violations that other steps on the ladder have failed to resolve, or a violation so serious that the Community Moderators determine there is no way to keep the community safe with this person as a member.
|
|
74
|
+
2) Consequence: Access to all community spaces, tools, and communication channels is removed. In general, permanent bans should be rarely used, should have strong reasoning behind them, and should only be resorted to if working through other remedies has failed to change the behavior.
|
|
75
|
+
3) Repair: There is no possible repair in cases of this severity.
|
|
76
|
+
|
|
77
|
+
This enforcement ladder is intended as a guideline. It does not limit the ability of Community Managers to use their discretion and judgment, in keeping with the best interests of our community.
|
|
78
|
+
|
|
79
|
+
|
|
80
|
+
## Scope
|
|
81
|
+
|
|
82
|
+
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public or other spaces. Examples of representing our community include using an official email address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
|
|
83
|
+
|
|
84
|
+
|
|
85
|
+
## Attribution
|
|
86
|
+
|
|
87
|
+
This Code of Conduct is adapted from the Contributor Covenant, version 3.0, permanently available at [https://www.contributor-covenant.org/version/3/0/](https://www.contributor-covenant.org/version/3/0/).
|
|
88
|
+
|
|
89
|
+
Contributor Covenant is stewarded by the Organization for Ethical Source and licensed under CC BY-SA 4.0. To view a copy of this license, visit [https://creativecommons.org/licenses/by-sa/4.0/](https://creativecommons.org/licenses/by-sa/4.0/)
|
|
90
|
+
|
|
91
|
+
For answers to common questions about Contributor Covenant, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq). Translations are provided at [https://www.contributor-covenant.org/translations](https://www.contributor-covenant.org/translations). Additional enforcement and community guideline resources can be found at [https://www.contributor-covenant.org/resources](https://www.contributor-covenant.org/resources). The enforcement ladder was inspired by the work of [Mozilla’s code of conduct team](https://github.com/mozilla/inclusion).
|
|
92
|
+
|
package/CONTRIBUTING.md
ADDED
|
@@ -0,0 +1,137 @@
|
|
|
1
|
+
# Contributing to CONTRIBUTING.md
|
|
2
|
+
|
|
3
|
+
First off, thanks for taking the time to contribute!
|
|
4
|
+
|
|
5
|
+
All types of contributions are encouraged and valued. See the [Table of Contents](#table-of-contents) for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions.
|
|
6
|
+
|
|
7
|
+
> And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
|
|
8
|
+
> - Star the project
|
|
9
|
+
> - Tweet about it
|
|
10
|
+
> - Refer this project in your project's readme
|
|
11
|
+
> - Mention the project at local meetups and tell your friends/colleagues
|
|
12
|
+
|
|
13
|
+
|
|
14
|
+
## Table of Contents
|
|
15
|
+
|
|
16
|
+
- [Code of Conduct](#code-of-conduct)
|
|
17
|
+
- [I Have a Question](#i-have-a-question)
|
|
18
|
+
- [I Want To Contribute](#i-want-to-contribute)
|
|
19
|
+
- [Reporting Bugs](#reporting-bugs)
|
|
20
|
+
- [Suggesting Enhancements](#suggesting-enhancements)
|
|
21
|
+
- [Your First Code Contribution](#your-first-code-contribution)
|
|
22
|
+
- [Improving The Documentation](#improving-the-documentation)
|
|
23
|
+
- [Styleguides](#styleguides)
|
|
24
|
+
- [Commit Messages](#commit-messages)
|
|
25
|
+
- [Join The Project Team](#join-the-project-team)
|
|
26
|
+
|
|
27
|
+
|
|
28
|
+
## Code of Conduct
|
|
29
|
+
|
|
30
|
+
This project and everyone participating in it is governed by the
|
|
31
|
+
[CONTRIBUTING.md Code of Conduct](blob/main/CODE_OF_CONDUCT.md).
|
|
32
|
+
By participating, you are expected to uphold this code. Please report unacceptable behavior
|
|
33
|
+
to <>.
|
|
34
|
+
|
|
35
|
+
|
|
36
|
+
## I Have a Question
|
|
37
|
+
|
|
38
|
+
> If you want to ask a question, we assume that you have read the available [Documentation]().
|
|
39
|
+
|
|
40
|
+
Before you ask a question, it is best to search for existing [Issues](/issues) that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
|
|
41
|
+
|
|
42
|
+
If you then still feel the need to ask a question and need clarification, we recommend the following:
|
|
43
|
+
|
|
44
|
+
- Open an [Issue](/issues/new).
|
|
45
|
+
- Provide as much context as you can about what you're running into.
|
|
46
|
+
- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
|
|
47
|
+
|
|
48
|
+
We will then take care of the issue as soon as possible.
|
|
49
|
+
|
|
50
|
+
|
|
51
|
+
|
|
52
|
+
## I Want To Contribute
|
|
53
|
+
|
|
54
|
+
> ### Legal Notice
|
|
55
|
+
> When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
|
|
56
|
+
|
|
57
|
+
### Reporting Bugs
|
|
58
|
+
|
|
59
|
+
|
|
60
|
+
#### Before Submitting a Bug Report
|
|
61
|
+
|
|
62
|
+
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
|
|
63
|
+
|
|
64
|
+
- Make sure that you are using the latest version.
|
|
65
|
+
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the [documentation](). If you are looking for support, you might want to check [this section](#i-have-a-question)).
|
|
66
|
+
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the [bug tracker](issues?q=label%3Abug).
|
|
67
|
+
- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
|
|
68
|
+
- Collect information about the bug:
|
|
69
|
+
- Stack trace (Traceback)
|
|
70
|
+
- OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
|
|
71
|
+
- Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
|
|
72
|
+
- Possibly your input and the output
|
|
73
|
+
- Can you reliably reproduce the issue? And can you also reproduce it with older versions?
|
|
74
|
+
|
|
75
|
+
|
|
76
|
+
#### How Do I Submit a Good Bug Report?
|
|
77
|
+
|
|
78
|
+
> You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to <>.
|
|
79
|
+
|
|
80
|
+
|
|
81
|
+
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
|
|
82
|
+
|
|
83
|
+
- Open an [Issue](/issues/new). (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
|
|
84
|
+
- Explain the behavior you would expect and the actual behavior.
|
|
85
|
+
- Please provide as much context as possible and describe the *reproduction steps* that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
|
|
86
|
+
- Provide the information you collected in the previous section.
|
|
87
|
+
|
|
88
|
+
Once it's filed:
|
|
89
|
+
|
|
90
|
+
- The project team will label the issue accordingly.
|
|
91
|
+
- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` tag will not be addressed until they are reproduced.
|
|
92
|
+
- If the team is able to reproduce the issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left to be [implemented by someone](#your-first-code-contribution).
|
|
93
|
+
|
|
94
|
+
|
|
95
|
+
|
|
96
|
+
|
|
97
|
+
### Suggesting Enhancements
|
|
98
|
+
|
|
99
|
+
This section guides you through submitting an enhancement suggestion for CONTRIBUTING.md, **including completely new features and minor improvements to existing functionality**. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
|
|
100
|
+
|
|
101
|
+
|
|
102
|
+
#### Before Submitting an Enhancement
|
|
103
|
+
|
|
104
|
+
- Make sure that you are using the latest version.
|
|
105
|
+
- Read the [documentation]() carefully and find out if the functionality is already covered, maybe by an individual configuration.
|
|
106
|
+
- Perform a [search](/issues) to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
|
|
107
|
+
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
|
|
108
|
+
|
|
109
|
+
|
|
110
|
+
#### How Do I Submit a Good Enhancement Suggestion?
|
|
111
|
+
|
|
112
|
+
Enhancement suggestions are tracked as [GitHub issues](/issues).
|
|
113
|
+
|
|
114
|
+
- Use a **clear and descriptive title** for the issue to identify the suggestion.
|
|
115
|
+
- Provide a **step-by-step description of the suggested enhancement** in as many details as possible.
|
|
116
|
+
- **Describe the current behavior** and **explain which behavior you expected to see instead** and why. At this point you can also tell which alternatives do not work for you.
|
|
117
|
+
- You may want to **include screenshots and animated GIFs** which help you demonstrate the steps or point out the part which the suggestion is related to. You can use [this tool](https://www.cockos.com/licecap/) to record GIFs on macOS and Windows, and [this tool](https://github.com/colinkeenan/silentcast) or [this tool](https://github.com/GNOME/byzanz) on Linux.
|
|
118
|
+
- **Explain why this enhancement would be useful** to most CONTRIBUTING.md users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
|
|
119
|
+
|
|
120
|
+
|
|
121
|
+
|
|
122
|
+
### Your First Code Contribution
|
|
123
|
+
|
|
124
|
+
|
|
125
|
+
### Improving The Documentation
|
|
126
|
+
|
|
127
|
+
|
|
128
|
+
## Styleguides
|
|
129
|
+
### Commit Messages
|
|
130
|
+
|
|
131
|
+
|
|
132
|
+
## Join The Project Team
|
|
133
|
+
|
|
134
|
+
|
|
135
|
+
|
|
136
|
+
## Attribution
|
|
137
|
+
This guide is based on the **contributing.md**. [Make your own](https://contributing.md/)!
|
package/README.md
CHANGED
|
@@ -21,25 +21,16 @@ This is a personal project and is not officially supported by Microsoft or Azure
|
|
|
21
21
|
## Install
|
|
22
22
|
|
|
23
23
|
```bash
|
|
24
|
-
npm install
|
|
24
|
+
npm install -g azdo-release-env
|
|
25
25
|
```
|
|
26
|
-
|
|
27
|
-
(Optional) Make the command available on your machine:
|
|
26
|
+
Or
|
|
28
27
|
|
|
29
28
|
```bash
|
|
30
|
-
|
|
29
|
+
npx azdo-release-env
|
|
31
30
|
```
|
|
32
31
|
|
|
33
32
|
## Usage
|
|
34
33
|
|
|
35
|
-
Run interactively:
|
|
36
|
-
|
|
37
|
-
```bash
|
|
38
|
-
npm start
|
|
39
|
-
```
|
|
40
|
-
|
|
41
|
-
Or (after `npm link`):
|
|
42
|
-
|
|
43
34
|
```bash
|
|
44
35
|
azdo-release-env
|
|
45
36
|
```
|
package/package.json
CHANGED
|
@@ -1,39 +1,39 @@
|
|
|
1
|
-
{
|
|
2
|
-
"name": "azdo-release-env",
|
|
3
|
-
"version": "1.0.
|
|
4
|
-
"description": "CLI tool for exporting Azure DevOps release environment variables",
|
|
5
|
-
"main": "src/index.js",
|
|
6
|
-
"bin": {
|
|
7
|
-
"azdo-release-env": "src/index.js"
|
|
8
|
-
},
|
|
9
|
-
"types": "types/index.d.ts",
|
|
10
|
-
"scripts": {
|
|
11
|
-
"start": "node src/index.js",
|
|
12
|
-
"test": "echo \"No tests yet\" && exit 0"
|
|
13
|
-
},
|
|
14
|
-
"keywords": [
|
|
15
|
-
"azure-devops",
|
|
16
|
-
"release",
|
|
17
|
-
"environment",
|
|
18
|
-
"variables",
|
|
19
|
-
"cli"
|
|
20
|
-
],
|
|
21
|
-
"author": "Joseph Cano",
|
|
22
|
-
"license": "MIT",
|
|
23
|
-
"repository": {
|
|
24
|
-
"type": "git",
|
|
25
|
-
"url": "https://github.com/Jcanotorr06/azdo-release-env"
|
|
26
|
-
},
|
|
27
|
-
"type": "module",
|
|
28
|
-
"dependencies": {
|
|
29
|
-
"@inquirer/prompts": "^8.3.0",
|
|
30
|
-
"@types/node": "^25.3.3",
|
|
31
|
-
"chalk": "^5.6.2",
|
|
32
|
-
"commander": "^14.0.3",
|
|
33
|
-
"execa": "^9.6.1",
|
|
34
|
-
"typescript": "^5.9.3"
|
|
35
|
-
},
|
|
36
|
-
"engines": {
|
|
37
|
-
"node": ">=20"
|
|
38
|
-
}
|
|
39
|
-
}
|
|
1
|
+
{
|
|
2
|
+
"name": "azdo-release-env",
|
|
3
|
+
"version": "1.0.1",
|
|
4
|
+
"description": "CLI tool for exporting Azure DevOps release environment variables",
|
|
5
|
+
"main": "src/index.js",
|
|
6
|
+
"bin": {
|
|
7
|
+
"azdo-release-env": "src/index.js"
|
|
8
|
+
},
|
|
9
|
+
"types": "types/index.d.ts",
|
|
10
|
+
"scripts": {
|
|
11
|
+
"start": "node src/index.js",
|
|
12
|
+
"test": "echo \"No tests yet\" && exit 0"
|
|
13
|
+
},
|
|
14
|
+
"keywords": [
|
|
15
|
+
"azure-devops",
|
|
16
|
+
"release",
|
|
17
|
+
"environment",
|
|
18
|
+
"variables",
|
|
19
|
+
"cli"
|
|
20
|
+
],
|
|
21
|
+
"author": "Joseph Cano",
|
|
22
|
+
"license": "MIT",
|
|
23
|
+
"repository": {
|
|
24
|
+
"type": "git",
|
|
25
|
+
"url": "https://github.com/Jcanotorr06/azdo-release-env"
|
|
26
|
+
},
|
|
27
|
+
"type": "module",
|
|
28
|
+
"dependencies": {
|
|
29
|
+
"@inquirer/prompts": "^8.3.0",
|
|
30
|
+
"@types/node": "^25.3.3",
|
|
31
|
+
"chalk": "^5.6.2",
|
|
32
|
+
"commander": "^14.0.3",
|
|
33
|
+
"execa": "^9.6.1",
|
|
34
|
+
"typescript": "^5.9.3"
|
|
35
|
+
},
|
|
36
|
+
"engines": {
|
|
37
|
+
"node": ">=20"
|
|
38
|
+
}
|
|
39
|
+
}
|