Skip to content

Float BCPlatform 29.0 version - #10610

Open
Maria Zhelezova (mazhelez) wants to merge 7 commits into
releases/29.xfrom
mazhelez/float-bcplatform-29x
Open

Float BCPlatform 29.0 version#10610
Maria Zhelezova (mazhelez) wants to merge 7 commits into
releases/29.xfrom
mazhelez/float-bcplatform-29x

Conversation

@mazhelez

@mazhelez Maria Zhelezova (mazhelez) commented Aug 25, 2026

Copy link
Copy Markdown
Contributor

What & why

Use the 29.0 major.minor selector for BCPlatform on the releases/29.x branch so builds resolve the latest matching 29.0 platform instead of requiring periodic four-part version updates. The existing platform setup scripts already resolve major.minor selectors through Resolve-PlatformVersion, and the package update automation preserves these selectors.

Linked work

Fixes #

How I validated this

  • I read the full diff and it contains only changes I intended.
  • I built the affected app(s) locally with no new analyzer warnings.
  • I ran the change in Business Central and confirmed it behaves as expected.
  • I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome (required — be specific: scenarios, commands, screenshots for UI changes)

  • Parsed build/Packages.json with ConvertFrom-Json successfully.
  • Ran build/scripts/tests/PlatformHelper.Test.ps1: 12 passed, 0 failed.
  • Resolved the configured 29.0 selector through Resolve-PlatformVersion; it returned the latest matching platform version.
  • Ran .github/actions/RunAutomation/UpdatePlatformVersion/run.ps1; it returned no updated files and left build/Packages.json unchanged because Update-PackageVersion preserves major.minor selectors.
  • No tests were added because the selector resolution and update guard already have focused coverage on this release branch.

Risk & compatibility

Low risk. Full four-part platform versions continue to work, while this release branch now opts into the existing major.minor resolution behavior. No application, schema, or runtime behavior changes.

AB#646623

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@mazhelez
Maria Zhelezova (mazhelez) requested review from a team August 25, 2026 12:21
@github-actions github-actions Bot added the Build: scripts & configs Build scripts and configuration files label Aug 25, 2026
@mazhelez

Copy link
Copy Markdown
Contributor Author

CI is currently blocked pending a valid Azure DevOps work-item reference (AB#) from a maintainer. The code change itself is complete and validated: the focused PlatformHelper tests pass, the 29.0 selector resolves successfully, and UpdatePlatformVersion preserves the major.minor selector without modifying Packages.json.

@github-actions github-actions Bot added this to the Version 29.0 milestone Aug 25, 2026
@JesperSchulz Jesper Schulz-Wedde (JesperSchulz) added the Team: Other GitHub request for other area than SCM, Finance or Integration label Aug 25, 2026
spetersenms
spetersenms previously approved these changes Aug 26, 2026
Floating to newer 29.0 compiler builds introduces repository-wide AA0181 and AA0233 analyzer regressions in required CI checks.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…at-bcplatform-29x

# Conflicts:
#	build/Packages.json
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…at-bcplatform-29x

# Conflicts:
#	build/Packages.json
Comment thread build/Packages.json
@github-actions

github-actions Bot commented Sep 7, 2026

Copy link
Copy Markdown
Contributor

⚠️ Stale Status Check Deleted

The Pull Request Build workflow run for this PR was older than 72 hours and has been deleted.

📋 Why was it deleted?

Status checks that are too old may no longer reflect the current state of the target branch. To ensure this PR is validated against the latest code and passes up-to-date checks, a fresh build is required.


🔄 How to trigger a new status check:

  1. 📤 Push a new commit to the PR branch, or
  2. 🔁 Close and reopen the PR

This will automatically trigger a new Pull Request Build workflow run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Build: scripts & configs Build scripts and configuration files Team: Other GitHub request for other area than SCM, Finance or Integration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants