New package OWASP.ThreatDragon 2.2.0 #184453
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- This version was released at the beginning of the year - The manifest was created with Komac - The idea here is to establish a baseline manifest that can then be updated with winget-releaser or directly using Komac # ------------------------ >8 ------------------------ # Do not modify or remove the line above. # Everything below it will be ignored. # # On branch adding-threatdragon # Changes to be committed: # new file: ThreatDragon/2.2.0/OWASP.ThreatDragon.installer.yaml # new file: ThreatDragon/2.2.0/OWASP.ThreatDragon.locale.en-US.yaml # new file: ThreatDragon/2.2.0/OWASP.ThreatDragon.yaml # diff --git a/manifests/o/OWASP/ThreatDragon/2.2.0/OWASP.ThreatDragon.installer.yaml b/manifests/o/OWASP/ThreatDragon/2.2.0/OWASP.ThreatDragon.installer.yaml new file mode 100644 index 00000000000..6cc80543eb3 --- /dev/null +++ b/manifests/o/OWASP/ThreatDragon/2.2.0/OWASP.ThreatDragon.installer.yaml @@ -0,0 +1,17 @@ +# Created with komac v2.6.0 +# yaml-language-server: $schema=https://aka.ms/winget-manifest.installer.1.6.0.schema.json + +PackageIdentifier: OWASP.ThreatDragon +PackageVersion: 2.2.0 +InstallerType: nullsoft +InstallModes: +- interactive +- silent +UpgradeBehavior: install +ReleaseDate: 2024-02-17 +Installers: +- Architecture: x86 + InstallerUrl: https://github.com/OWASP/threat-dragon/releases/download/v2.2.0/Threat-Dragon-ng-Setup-2.2.0.exe + InstallerSha256: D5295584C6EDBBFA8515218C173E9125ADD690D5DEDE37702FC0B7D7FDD5E93A +ManifestType: installer +ManifestVersion: 1.6.0 diff --git a/manifests/o/OWASP/ThreatDragon/2.2.0/OWASP.ThreatDragon.locale.en-US.yaml b/manifests/o/OWASP/ThreatDragon/2.2.0/OWASP.ThreatDragon.locale.en-US.yaml new file mode 100644 index 00000000000..5b5bb573f9f --- /dev/null +++ b/manifests/o/OWASP/ThreatDragon/2.2.0/OWASP.ThreatDragon.locale.en-US.yaml @@ -0,0 +1,30 @@ +# Created with komac v2.6.0 +# yaml-language-server: $schema=https://aka.ms/winget-manifest.defaultLocale.1.6.0.schema.json + +PackageIdentifier: OWASP.ThreatDragon +PackageVersion: 2.2.0 +PackageLocale: en-US +Publisher: OWASP +PublisherUrl: https://owasp.org/ +PublisherSupportUrl: https://github.com/OWASP/threat-dragon/issues/new/choose +Author: OWASP contributors +PackageName: Threat-Dragon-ng +PackageUrl: https://github.com/OWASP/threat-dragon/releases +License: Apache-2.0 +LicenseUrl: https://github.com/OWASP/threat-dragon/blob/main/license.txt +Copyright: Copyright © 2015 - 2024 OWASP +CopyrightUrl: https://github.com/OWASP/threat-dragon +ShortDescription: Threat Dagon is an open source threat modeling tool and is an official OWASP project. It is used to draw threat modeling diagrams and to list threats for elements in the diagram +Description: | + OWASP Threat Dragon is a free, open-source, cross-platform threat modeling application. It is used to draw threat modeling diagrams and to list threats for elements in the diagram along with their remediations. + Threat Dragon is designed to be accessible for various types of teams, with an emphasis on flexibility and simplicity. It is an OWASP Lab Project and follows the values and principles of the threat modeling manifesto +Moniker: threatdragon +Tags: +- owasp +- owasp-threat-dragon +- sdlc +- threat-dragon +- threat-modeling +ReleaseNotesUrl: https://github.com/OWASP/threat-dragon/releases/tag/v2.2.0 +ManifestType: defaultLocale +ManifestVersion: 1.6.0 diff --git a/manifests/o/OWASP/ThreatDragon/2.2.0/OWASP.ThreatDragon.yaml b/manifests/o/OWASP/ThreatDragon/2.2.0/OWASP.ThreatDragon.yaml new file mode 100644 index 00000000000..a34a372dc80 --- /dev/null +++ b/manifests/o/OWASP/ThreatDragon/2.2.0/OWASP.ThreatDragon.yaml @@ -0,0 +1,8 @@ +# Created with komac v2.6.0 +# yaml-language-server: $schema=https://aka.ms/winget-manifest.version.1.6.0.schema.json + +PackageIdentifier: OWASP.ThreatDragon +PackageVersion: 2.2.0 +DefaultLocale: en-US +ManifestType: version +ManifestVersion: 1.6.0
|
|
|
/AzurePipelines run |
assarbad
added a commit
to assarbad/threat-dragon
that referenced
this pull request
Oct 19, 2024
- This is meant to automate releases to winget-pkgs - Resolves OWASP#848 and should work as soon as microsoft/winget-pkgs#184453 has been merged (baseline manifest for the 2.2.0 version) - DO NOT MERGE BEFORE PREREQUISITES ARE IN PLACE (see below) ## Instructions for prerequisites The `WINGET_TOKEN` needs to be created and registered in the repo _which does the release_. For good measure we need to clone `winget-pkgs` on the same user (or org) or set via `fork-user` it as per the README for [winget-releaser](https://github.com/vedantmgoyal9/winget-releaser). Configure the [Pull app](https://github.com/apps/pull) to keep the `winget-pkgs` fork in sync with its upstream. That `winget-pkgs` fork is going to be the _source_ of the PR filed at `microsoft/winget-pkgs` and the PRs are being opened on behalf of the owner of the used token. 1. Head to https://github.com/settings/tokens and create a new (classic) personal access token with _only_ the `public_repo` scope activated for it 2. In https://github.com/OWASP/threat-dragon/settings/secrets/actions create a secret named WINGET_TOKEN (as per vedantmgoyal9/winget-releaser) 3. Merge this PR 4. Create a (subsequent) release
|
/AzurePipelines run |
wingetbot
added
New-Package
Azure-Pipeline-Passed
|
The only way that I can see Policy 2.8 applying is through overzealous advertising. |
stephengillie
added
Validation-Completed
|
Verify: |
stephengillie
approved these changes
Oct 22, 2024
microsoft-github-policy-service
bot
added
the
Moderator-Approved
![microsoft-github-policy-service[bot]](https://avatars.githubusercontent.com/in/95686?s=60&v=4){kind=small}
microsoft-github-policy-service
bot
merged commit 501695b
into
microsoft:master
2 checks passed
|
Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist for Pull Requests
Manifests
winget validate --manifest <path>?winget install --manifest <path>?Note:
<path>is the directory's name containing the manifest you're submitting.This is in preparation for
winget-releaserautomation on the project, see OWASP/threat-dragon#848.Microsoft Reviewers: Open in CodeFlow