Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: rokucommunity/brighterscript
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: master
Choose a base ref
...
head repository: plexinc/brighterscript
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: xelp/main
Choose a head ref
Checking mergeability… Don’t worry, you can still create the pull request.
  • 5 commits
  • 9 files changed
  • 1 contributor

Commits on Mar 12, 2026

  1. Configuration menu
    Copy the full SHA
    e7942cc View commit details
    Browse the repository at this point in the history
  2. [XELP] GHA shadow release

    ljunkie committed Mar 12, 2026
    Configuration menu
    Copy the full SHA
    61fdb7f View commit details
    Browse the repository at this point in the history

Commits on Aug 28, 2026

  1. Publish releases to GitHub Packages under the @plexinc scope.

    Replace the git tag and xelp/dist shadow release with a workflow that publishes
    to GitHub Packages as @plexinc/<name>, matching how the other Plex client repos
    consume private packages. Authentication is the workflow GITHUB_TOKEN, so the
    repository stores no publishing secret, and the package name is rewritten in CI
    rather than on xelp/main, leaving upstream merges unaffected.
    
    The lint and test suites previously ran as a side effect of npm version, which
    triggers preversion. Setting the version with npm pkg set skips lifecycle
    scripts, so they now run as their own steps.
    
    Consumers keep the upstream package name by installing through an npm alias, so
    imports, bin names and plugin references do not change.
    ljunkie committed Aug 28, 2026
    Configuration menu
    Copy the full SHA
    4e25a0e View commit details
    Browse the repository at this point in the history
  2. Disable the shadow release in favour of the npm release.

    Both workflows compute the same MAJOR.MINOR.<date><PATCH> version and so want
    the same tag, and the shadow release force pushes it, so running the two against
    one commit means one clobbers the other. Park the shadow release rather than
    delete it, matching the .disabled convention already used in this family of
    repos, so restoring it is a rename.
    
    roku-client is the only consumer of this fork, and it keeps installing from the
    existing git tag until it moves to the @plexinc package, so nothing depends on
    this workflow staying runnable in the meantime.
    ljunkie committed Aug 28, 2026
    Configuration menu
    Copy the full SHA
    ac24c9d View commit details
    Browse the repository at this point in the history
  3. Scope the registry token to the steps that use npm.

    The token was set on the two steps that obviously needed it, the published
    version check and the publish. That is enough here, because this package has no
    @plexinc dependencies of its own, but not in the forks that do:
    brighterscript-formatter cannot run npm ci without it.
    
    Give it to the install step as well, and keep it off the job so it stays out of
    the environment of steps that never reach the network. This restores the file to
    being identical to the copies in the other two forks.
    ljunkie committed Aug 28, 2026
    Configuration menu
    Copy the full SHA
    09bf8f8 View commit details
    Browse the repository at this point in the history
Loading