Releases: igoravl/TfsCmdlets
Release 2.9.2+3932.5
This release fixes a bug in Get-TfsGitItem cmdlet.
Fixes
Get-TfsGitItem: Fixed an issue where the cmdlet would fail when specifying a commit SHA.
Release 2.9.1+3877.9
This release fixes a critical bug in Set-TfsWorkItem, among other improvements.
Fixes
Get-TfsVersion: Adds support for Azure DevOps Services version "20" (currently mapped to 2022)Remove-TfsTeamProject: Removes a double-confirmation prompt when using the-Hardswitch, simplifying the deletion processSet-TfsWorkItem: Fixed an issue where the actual work item ID wasn't being used when retrieving work item type information, causing some field updates to fail
Release 2.9.0+3583.93
This release adds new process-related cmdlets along with some fixes, enhancements and a couple minor but potentially breaking changes.
New cmdlets
Get-ProcessFieldDefinition: Gets information from one or more organization-wide work item fieldsNew-ProcessFieldDefinition: Creates a new organization-wide work item fieldRemove-ProcessFieldDefinition: Removes an organization-wide work item field
Fixes
Get-TfsArtifact: Fixed an issue where it wouldn't list deleted packages.Get-TfsArtifactFeed: Fixed an issue where it would ignore the -Project argument and thus not filter feeds by project.Get-TfsWorkItemTag: Fixed an issue where it would fail when given a list of tags as input.Get-TfsWorkItemType: Fixed an issue where it would throw a "Parameter count mismatch" error when trying to get the work item type of a given work item.
Changes and enhancements
Get-TfsGitBranch: Added a new-Compareargument to to get the "Compare" (base) branch of a given repository.Connect-TfsTeamProjectCollection,Connect-TfsOrganization: Now it throws an error when trying to connect with invalid credentials instead of silently going into "anonymous mode". That help preventing subtle script errors where the lack of authorization would only be noticed later in the script, when trying to actually perform some command that required valid credentials. Now you get the warning that something is wrong as early in the script as possible.
Breaking changes
Get-TfsGitBranch:-Repositoryparameter is now mandatory. This is to reduce the ambiguity of the command when omitting that argument. Scripts that rely on the old behavior may need to be updated.Get-TfsGitBranchPolicy: Both-Branchand-Repositoryparameters are now mandatory. This is to reduce the ambiguity of the command when omitting those arguments. Scripts that rely on the old behavior may need to be updated.
Release 2.8.2+3561.26
This release brings some fixes and enhancements.
Enhancements
Add-TfsWorkItemLink: Added support for specifying the arguments-SuppressNotificationand-BypassRulesto suppress notifications and bypass rules when adding a work item link.- Now when when a cmdlet fails, a full exception dump will be sent to the verbose output stream in addition to the short error message sent to the error stream. So, if your script is failing and you don't know why, you can enable the verbose output to get more information about the error.
Fixes
- Fixed an issue where the
Get-TfsTeamcmdlet would not work when specifying the-Defaultparameter. - Fixed an issue where
Invoke-TfsRestApiwould ignore the parameters passed via the-Parametersargument [#228]
Release 2.8.1+3553.1
This release fixes an issue with the New-TfsUser cmdlet.
Fixes
- Fixed an issue where the
New-TfsUsercmdlet could throw an error when not supplying project entitlements via the -Project argument.
Release 2.8.0+3546.2
This release adds two new cmdlets: New-TfsUser and Remove-TfsUser.
New cmdlets
New-TfsUser: Creates a new user in the organization and optionally adds them to projects.Remove-TfsUser: Removes a user from the organization.
Release 2.7.1+3540.1
This release fixes an issue with the Chocolatey publishing process. No changes have been made to the cmdlets.
Release 2.7.0+3540.2
This release adds support for suppressing notifications when creating or updating work items.
New features
- Adds
-SuppressNotificationsswitch toNew-TfsWorkItemandSet-TfsWorkItemto suppress notifications when creating or updating work items. This is useful when you are creating or updating a large number of work items and don't want to flood the notification feed of team members.
Release 2.6.1+3491.1
Ouch! It's been a while since the last release! Sometimes life gets in the way, but I'm back!
This release fixes bugs in Get-TfsWorkItem, Get-TfsArea, Get-TfsIteration, Invoke-TfsRestApi, New-TfsTeam and Set-TfsTeam.
Fixes
- Fixes #211, where
Get-TfsWorkItemwould throw an error when the-Fieldsparameter was "*". - Fixes a bug in
Invoke-TfsRestApiwhere Azure DevOps APIs whose responses were missing thecontent-typeheader would throw an error. - Fixes a bug in
Get-TfsAreaandGet-TfsIterationwhere team projects containing Regex-reserved characters (such as parentheses) would throw an error. This bug would indirectly affectNew-TfsTeamandSet-TfsTeamdue to their reliance on the same underlying class to handle area and iteration paths when creating/updating teams. - Fixes a bug in
Get-TfsWorkItemwhere the-AreaPathand-IterationPathparameters would not work when the specified path either started with a backslash or did not contain the team project name. - Adds the installed module version to the Azure DevOps Shell startup command to prevent loading an older version of the module when the PSModulePath variable contains an older version of the module listed earlier in the search path.
Release 2.6.0+2898.5
This release fixes a bug in Get-TfsWorkItemQuery and Get-TfsWorkItemQueryFolder, and adds two new cmdlets.
New cmdlets
Undo-TfsWorkItemQueryRemovalandUndo-TfsWorkItemQueryFolderRemovalallow you to undo the deletion of a query or query folder. This is useful when you accidentally delete a query or query folder and want to restore it.
To restore a deleted query:
# You can either pipe the deleted query from Get-TfsWorkItemQuery to Undo-TfsWorkItemQueryRemoval...
Get-TfsWorkItemQuery 'My Deleted Query' -Scope Personal -Deleted | Undo-TfsWorkItemQueryRemoval
# ... or you can specify the query directly when calling Undo-TfsWorkItemQueryRemoval
Undo-TfsWorkItemQueryRemoval 'My Deleted Query' -Scope PersonalThe same applies to query folders - with the distinction that folder can be restored recursively by specifying the -Recursive switch. When -Recursive is omitted, only the folder itself is restored, without any of its contents. You can then restore its contents by issuing further calls to Undo-TfsWorkItemQueryRemoval and/or Undo-TfsWorkItemQueryFolderRemoval.
# You can either pipe the deleted folder from Get-TfsWorkItemQueryFolder to Undo-TfsWorkItemQueryFolderRemoval...
Get-TfsWorkItemQueryFolder 'My Deleted Folder' -Scope Personal -Deleted | Undo-TfsWorkItemQueryRemoval -Recursive
# ... or you can specify the folder directly when calling Undo-TfsWorkItemQueryFolderRemoval
Undo-TfsWorkItemQueryFolderRemoval 'My Deleted Folder' -Scope Personal -RecursiveFixes
- Fixes a bug in
Get-TfsWorkItemQueryandGet-TfsWorkItemQueryFolderwhere the-Deletedswitch was not respected and deleted items would not be returned.