Draft
Conversation
## PR Title Format **Required Format:** `[Keyword1] [Keyword2]: Description` - **Keyword1:** `major`, `minor`, or `patch` (case-insensitive) - **Keyword2:** `feature`, `bugfix`, `engg`, or `tests` (case-insensitive) **Examples:** - `[MAJOR] [Feature]: new API` - `[minor] [bugfix]: fix crash` - `[PATCH] [tests]: add coverage` ## Proposed changes Trying to get rid of this from appearing in git <img width="717" height="853" alt="Screenshot 2026-02-26 at 12 55 31 PM" src="https://github.com/user-attachments/assets/d8b59052-9090-4167-9873-2acd9cc73ef4" /> ## Type of change - [ ] Feature work - [ ] Bug fix - [ ] Documentation - [x] Engineering change - [ ] Test - [ ] Logging/Telemetry ## Risk - [ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes) - [ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features) - [x] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) ## Additional information
…hod changed in CommonCore (#2880) ## PR Title Format **Required Format:** `[Keyword1] [Keyword2]: Description` - **Keyword1:** `major`, `minor`, or `patch` (case-insensitive) - **Keyword2:** `feature`, `bugfix`, `engg`, or `tests` (case-insensitive) **Examples:** - `[MAJOR] [Feature]: new API` - `[minor] [bugfix]: fix crash` - `[PATCH] [tests]: add coverage` ## Proposed changes Describe what this PR is trying to do. ## Type of change - [x] Feature work - [ ] Bug fix - [ ] Documentation - [ ] Engineering change - [ ] Test - [ ] Logging/Telemetry ## Risk - [ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes) - [ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features) - [x] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) ## Additional information [AB#3403593](https://identitydivision.visualstudio.com/fac9d424-53d2-45c0-91b5-ef6ba7a6bf26/_workitems/edit/3403593) --------- Co-authored-by: kai <[email protected]> Co-authored-by: Juan Arias <[email protected]>
Merge Release 2.9.0 back to Dev ## Type of change - [ ] Feature work - [ ] Bug fix - [ ] Documentation - [x] Engineering change - [ ] Test - [ ] Logging/Telemetry ## Risk - [ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes) - [ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features) - [x] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) ## Additional information --------- Co-authored-by: galwarsamy <[email protected]> Co-authored-by: Gowri Alwarsamy <[email protected]> Co-authored-by: Juan Arias Roldan <[email protected]> Co-authored-by: Juan Arias <[email protected]> Co-authored-by: Sergei Demchenko <[email protected]>
## Proposed changes Update common core to dev ## Type of change - [ ] Feature work - [ ] Bug fix - [ ] Documentation - [ ] Engineering change - [ ] Test - [ ] Logging/Telemetry ## Risk - [ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes) - [ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features) - [x] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) ## Additional information
…k in to MSAL iOS xcframework (#2850) ## Proposed changes VisionOS is missing from the MSAL iOS xcframework when consumed via SPM. This PR adds fixes to include it ## Type of change - [ ] Feature work - [x] Bug fix - [ ] Documentation - [ ] Engineering change - [ ] Test - [ ] Logging/Telemetry ## Risk - [ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes) - [ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features) - [x] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) ## Additional information
The pipeline gets timed out and fails. Increasing the timeout limit to 60 mins --------- Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: ameyapat <[email protected]>
…ude the right bridging header in common-core (#2846) ## PR Title Format **Required Format:** `[Keyword1] [Keyword2]: Description` - **Keyword1:** `major`, `minor`, or `patch` (case-insensitive) - **Keyword2:** `feature`, `bugfix`, `engg`, or `tests` (case-insensitive) **Examples:** - `[MAJOR] [Feature]: new API` - `[minor] [bugfix]: fix crash` - `[PATCH] [tests]: add coverage` ## Proposed changes This PR refactors the podspec and adds a macro so that the right bridging header is imported in common-core when generating pod for MSAL. ## Type of change - [x] Feature work - [ ] Bug fix - [ ] Documentation - [ ] Engineering change - [ ] Test - [ ] Logging/Telemetry ## Risk - [ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes) - [x] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features) - [ ] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) ## Additional information --------- Co-authored-by: Copilot <[email protected]>
## Proposed changes Remove accidentally added MSAL.zip ## Type of change - [ ] Feature work - [x] Bug fix - [ ] Documentation - [ ] Engineering change - [ ] Test - [ ] Logging/Telemetry ## Risk - [ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes) - [ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features) - [x] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) ## Additional information
## PR Title Format **Required Format:** `[Keyword1] [Keyword2]: Description` - **Keyword1:** `major`, `minor`, or `patch` (case-insensitive) - **Keyword2:** `feature`, `bugfix`, `engg`, or `tests` (case-insensitive) **Examples:** - `[MAJOR] [Feature]: new API` - `[minor] [bugfix]: fix crash` - `[PATCH] [tests]: add coverage` ## Proposed changes Describe what this PR is trying to do. ## Type of change - [ ] Feature work - [ ] Bug fix - [ ] Documentation - [ ] Engineering change - [ ] Test - [ ] Logging/Telemetry ## Risk - [ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes) - [ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features) - [ ] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) ## Additional information Co-authored-by: kai <[email protected]>
…rInvalidRequestResetPasswordRequired (#2867) ## PR Title Format **Required Format:** `[Keyword1] [Keyword2]: Description` - **Keyword1:** `major`, `minor`, or `patch` (case-insensitive) - **Keyword2:** `feature`, `bugfix`, `engg`, or `tests` (case-insensitive) **Examples:** - `[MAJOR] [Feature]: new API` - `[minor] [bugfix]: fix crash` - `[PATCH] [tests]: add coverage` ## Proposed changes Add additional error handling in MSAL when we receive the following error combination from ESTS: error = MSIDServerInvalidRequest error_code = 50142 (SecureChangePasswordDueToConditionalAccess) We are adding this change such that OneAuth has ability to map this specific error to interaction required. ## Type of change - [ ] Feature work - [ ] Bug fix - [ ] Documentation - [X] Engineering change - [ ] Test - [ ] Logging/Telemetry ## Risk - [ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes) - [ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features) - [X] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) ## Additional information --------- Co-authored-by: Fidelia Nawar <[email protected]> Co-authored-by: Copilot <[email protected]>
…ng bound app refresh tokens (#2896) ## PR Title Format **Required Format:** `[Keyword1] [Keyword2]: Description` - **Keyword1:** `major`, `minor`, or `patch` (case-insensitive) - **Keyword2:** `feature`, `bugfix`, `engg`, or `tests` (case-insensitive) **Examples:** - `[MAJOR] [Feature]: new API` - `[minor] [bugfix]: fix crash` - `[PATCH] [tests]: add coverage` ## Proposed changes Adding a property in MSAL global config that allows app to opt into using Bound app refresh tokens. ## Type of change - [x] Feature work - [ ] Bug fix - [ ] Documentation - [ ] Engineering change - [ ] Test - [ ] Logging/Telemetry ## Risk - [ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes) - [x] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features) - [ ] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) ## Additional information --------- Co-authored-by: Copilot Autofix powered by AI <[email protected]>
…2898) ## PR Title Format **Required Format:** `[Keyword1] [Keyword2]: Description` - **Keyword1:** `major`, `minor`, or `patch` (case-insensitive) - **Keyword2:** `feature`, `bugfix`, `engg`, or `tests` (case-insensitive) **Examples:** - `[MAJOR] [Feature]: new API` - `[minor] [bugfix]: fix crash` - `[PATCH] [tests]: add coverage` ## Proposed changes Describe what this PR is trying to do. ## Type of change - [ ] Feature work - [ ] Bug fix - [ ] Documentation - [ ] Engineering change - [ ] Test - [ ] Logging/Telemetry ## Risk - [ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes) - [ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features) - [ ] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) ## Additional information --------- Co-authored-by: kai <[email protected]>
Removes the automated GitHub issue creation functionality that triggers on pipeline failures in `automation.yml`. ## Changes - **UsePythonVersion@0 task** - Python environment setup - **github3.py installation** - Bash task installing the Python REST API client - **PythonScript@0 task** - Script that created issues with `@AzureAD/appleidentity` mentions on automation failures All three tasks were conditionally executed on failure and are no longer needed. <!-- START COPILOT CODING AGENT SUFFIX --> <!-- START COPILOT ORIGINAL PROMPT --> <details> <summary>Original prompt</summary> > On automation.yml, Remove the tasks UsePythonVersion, PythonScript 'Create Issue if pipeline fails' and task that install Github3 library </details> <!-- START COPILOT CODING AGENT TIPS --> --- 💬 We'd love your input! Share your thoughts on Copilot coding agent in our [2 minute survey](https://gh.io/copilot-coding-agent-survey). --------- Co-authored-by: copilot-swe-agent[bot] <[email protected]> Co-authored-by: ameyapat <[email protected]> Co-authored-by: Ameya Patil <[email protected]>
…ncy guard (#2900) ## Proposed changes Enhances the AI auto-reply workflow (`.github/workflows/ai-issues-auto-reply.yml`) with three improvements: 1. **Label-based trigger** – The workflow now also fires on the `labeled` event. Adding the `target-ai-triage` label to any issue triggers the AI triage bot, useful for retrying on old issues. 2. **Retry on 429** – The GitHub Models API call now retries once on HTTP 429 (rate limit), respecting the `Retry-After` header (capped at 60 s, default 30 s). 3. **Concurrency guard** – Added a `concurrency` group keyed by issue number to prevent duplicate AI replies from racing past the gate check. 4. **Bug fix** – `TARGET_FOR_AI_TRIAGE_LABEL` env var is now passed to the "Post reply" step so the trigger label is properly removed after replying. ## Type of change - [x] Engineering change ## Risk - [x] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) --------- Co-authored-by: Juan Arias Roldan <[email protected]>
## PR Title Format **Required Format:** `[Keyword1] [Keyword2]: Description` - **Keyword1:** `major`, `minor`, or `patch` (case-insensitive) - **Keyword2:** `feature`, `bugfix`, `engg`, or `tests` (case-insensitive) **Examples:** - `[MAJOR] [Feature]: new API` - `[minor] [bugfix]: fix crash` - `[PATCH] [tests]: add coverage` ## Proposed changes Describe what this PR is trying to do. ## Type of change - [x] Feature work - [ ] Bug fix - [ ] Documentation - [ ] Engineering change - [ ] Test - [ ] Logging/Telemetry ## Risk - [ ] High – Errors could cause MAJOR regression of many scenarios. (Example: new large features or high level infrastructure changes) - [ ] Medium – Errors could cause regression of 1 or more scenarios. (Example: somewhat complex bug fixes, small new features) - [x] Small – No issues are expected. (Example: Very small bug fixes, string changes, or configuration settings changes) ## Additional information
This file contains hidden or 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
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.
Pushing release draft PR for MSAL X.X.2 into main. Common Core submodule has been updated to point to temp_release/X.X.2 and changelog.txt has been updated.