dallasgroot/Gimp
dallasgroot/Gimp
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
Gimp/build/windows/store
History
Bruno Lopes 863d601a6b
Revert "build: Make CI_COMMIT_TAG check more robust" 
This reverts commit 4d7135f6f2.

This also reverts 3d72f1c08b.

The main reason is that it does not work on PowerShell due
to the tricky way it handles error.
2025-11-17 12:22:06 -03:00
..
3_dist-gimp-winsdk.ps1 Revert "build: Make CI_COMMIT_TAG check more robust" 2025-11-17 12:22:06 -03:00
AppxManifest.xml build/windows, devel-docs: The minimum Windows version is actually 10.0.18362.0 2025-08-18 15:10:27 -03:00
pseudo-gimp_2024.pfx build/windows: Renew pseudo-gimp*.pfx certificate and document it 2024-12-21 08:40:07 -03:00
README.md build: Document the importance of double-check on Partner Center and Snapcraft 2025-10-07 17:00:56 -03:00

README.md

GIMP MSIX HowTo

Stable and Development releases

The MS Store/Partner Center hosts our stable and development point releases: https://partner.microsoft.com/dashboard/apps-and-games/overview

Base rule to update the "GIMP" or "GIMP (Preview)" entry:

  • Regularly, a .msixupload will be generated at each tagged commit. It also can be with a custom pipeline valuating GIMP_CI_MS_STORE variable to ${REVISION} as briefly explained in "Versioning the MSIX" section. In the process, it will be auto submitted (without changelog) to Partner Center. (Any case, please double-check on Partner Center if everything is done.)

Maintaining the MSIX

If the submission from CI does not work, check on MS Entra Admin Center for the client secret of 'GITLAB_CI' app. If expired, create a new one and add it on GitLab as a masked, hidden and protected variable. Then, retrigger the Store job. That is usually faster than doing a manual submission as per instructions below:

  1. The link above will open 'Partner Center', the frontend to submit .msixupload

  2. With your Microsoft Entra ID account (@*onmicrosoft.com), log-in as customary

  3. Clicking on the "Start update" button will make possible to change some things. Only 'Packages' and 'Store listings' sections are needed. On 'Packages' you will add the generated .msixupload and on 'Store listings' the brief changelog.

If the .msix* starts to be refused to certification or to self-signing, run build\windows\store\3_dist-gimp-winsdk.ps1 WACK locally to see if it still complies with the latest Windows policies. Make sure to update WinSDK.

Versioning the MSIX