Repository navigation
Build and release the app package in CI - #2
Merged
Merged
Conversation
Every pull request and push to main validates appPackage and builds the production package as a run artifact. Each new manifest version that reaches main is published as a GitHub release with a versioned zip for Partner Center and eon-m365-copilot.zip, so the docs can link to releases/latest/download/eon-m365-copilot.zip. Pull requests that change appPackage must bump the version. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Admins who add Eon to Microsoft 365 Copilot by uploading the app package need a stable place to download it, and the docs (eon-io/docs#807) link to it. Today the package only exists when someone builds it locally.
This adds
.github/workflows/app-package.yml:main: runsbuild_package.py --check, builds the production package (https://mcp.eon.io/mcpwith the production OAuth registration), and attacheseon-m365-copilot-<version>.zipandeon-m365-copilot.zipto the run as an artifact.appPackage/must bumpversioninappPackage/manifest.json. Otherwise the change would never be released, and Microsoft 365 treats an upload with an existing version as the same app.mainis published as GitHub releasev<version>with both zips, sohttps://github.com/eon-io/m365-copilot-eon-plugin/releases/latest/download/eon-m365-copilot.zipalways serves the newest package. When the release for that version already exists, the job skips publishing (the run artifact still has the zip).The README links the download and describes the CI.
Notes:
env. It isn't a secret: every released package carries it inmanifest.jsonandai-plugin.json.checkoutv7.0.1,upload-artifactv7.0.2,download-artifactv8.0.2). The release step uses the preinstalledghCLI. Only the release job getscontents: write.Testing:
actionlintv1.7.12: clean.--checkpasses, and the built zip's contents are identical to the production 1.0.0 package used for Partner Center.🤖 Generated with Claude Code