Release JumpCloud PowerShell Module v3.1.0

[junioralmeida-82]

…tion

Issues

CUT-5114 - JumpCloud PowerShell Module Release v3.1.0

What does this solve?

-Updates the JumpCloud PowerShell Module to version 3.1.0.

-Fixes a parameter alias conflict in Get-JCPolicyGroupMember and Set-JCPolicyGroupMember where the id alias was missing or incorrectly formatted.

-Synchronizes and updates the module documentation (Markdown files) to reflect version 3.1.0 changes.

-Security Note: This is a clean PR. The nested repository issue from the previous attempt was resolved by physically removing the untracked metadata and updating the .gitignore to prevent future recursion issues.

Is there anything particularly tricky?

-No. The fix involved simple alias adjustments and a full rebuild of the help files using Build-HelpFiles.ps1.

How should this be tested?

1. Import the module from this branch.

2. Run Get-JCPolicyGroupMember -id to ensure the alias is working correctly.

3. Verify that the JumpCloud.psd1 manifest shows version 3.1.0.

Screenshots

---

Note

Medium Risk
Medium risk because it introduces a new exported cmdlet and changes parameter naming/aliases for Get-JCPolicyGroupMember, which could affect existing scripts relying on the old parameter name or alias behavior.

Overview
Releases JumpCloud PowerShell Module v3.1.0 by bumping the manifest/docs versions and updating the changelog.

Adds a new Set-JCPolicyGroupMember function (exported in JumpCloud.psd1) to manage policy memberships in policy groups via the V2 SDK, and fixes policy group member cmdlet parameter consistency by renaming PolicyGroupID to GroupId while retaining id/_id aliases.

Regenerates/synchronizes help content: standardizes docs frontmatter Module Name to jumpcloud, adds new markdown/XML help for Set-JCPolicyGroupMember, and updates help text/examples for Connect-JCOnline/Set-JCSettingsFile around environment/region selection.

^{Reviewed by Cursor Bugbot for commit 2f91eb3. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 2 potential issues.

^{Reviewed by Cursor Bugbot for commit 6a5bb51. Configure here.}

[cursor]

Renamed parameter lacks backward-compatible alias breaking existing usage

High Severity

The parameter $PolicyGroupID was renamed to $GroupId but no backward-compatible alias for PolicyGroupID was added. The aliases only include id and _id. This breaks all existing scripts and tests that use -PolicyGroupID, including the module's own test file (Get-JCPolicyGroupMember.Tests.ps1 lines 20, 28), the documentation example in Get-JCPolicyGroupMember.md line 35, and the help XML example at line 6823. Adding 'PolicyGroupID' to the [Alias()] attribute would preserve backward compatibility.

Additional Locations (1)

• [PowerShell/JumpCloud Module/en-Us/JumpCloud-help.xml#L6736-L6748](https://github.com/TheJumpCloud/support/blob/6a5bb5168a4b37938e28af7e08db34ba31afad92/PowerShell/JumpCloud Module/en-Us/JumpCloud-help.xml#L6736-L6748)

 

^{Reviewed by Cursor Bugbot for commit 6a5bb51. Configure here.}

[cursor]

Pipeline results overwritten instead of accumulated in Process block

Medium Severity

The Process block uses $Results = (assignment) instead of $Results += (append). Since Body and InputObject parameters accept pipeline input via ValueFromPipeline, multiple pipeline items will each overwrite $Results, and only the last item's result is returned. Other module functions like Add-JCAssociation correctly use $Results += to accumulate results across pipeline iterations.

 

^{Reviewed by Cursor Bugbot for commit 6a5bb51. Configure here.}

[junioralmeida-82]

Hey @jworkmanjc , I've updated the manifest and changelog with today's date and confirmed the staging environment parameters. The PR is ready for your final review!