feat: add selected Channel brand icon - #6
Merged
Merged
Conversation
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
1 participant
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.
Channels now exports the selected silver confluence brand artwork through the existing public
CordisXPluginBrandIconmodule API, so Host-owned plugin lists can consume it. The unchanged 256×256 PNG is tracked atassets/channel.pngand included in package distribution; semantic menu and action icons remain unchanged.The bundled-module test checks PNG identity, dimensions and the selected SHA256 (
8a989a7a2c83d66d4b10381e77bf596222f8301980518a86b4fbbcad006c1e0d). The existingnpm run checkadditionally packs the plugin and compares the archived PNG and runtime module with the validated build. A small generator maintains the source icon export from the PNG for source and bundled loading.Validation: local dprint and diff checks passed. Full owner gate and package verification run in existing GitHub CI to avoid concurrent local Git dependency builds. Native Host visual acceptance is not claimed. Package stays private at 0.1.0; distribution is repository source, with no npm release or new release channel.