Quarterly Maintenance: Upgrade Matomo and Premium Plugins and Set CPU Architecture - #40
Merged
Conversation
Why these changes are being made: It's time for the quarterly maintenance on Matomo! There is a new version of the Matomo Docker container (and it does require a database upgrade after installation). There are also updates to the premium plugins, but those will be in a separate commit. How these changes are implemented: * Update .gitignore * Remove unnecessary .deb file * Update Dockerfile to pull latest version of Matomo (5.12.0) Related Jira tickets: * https://mitlibraries.atlassian.net/browse/INFRA-656
Why these changes are being introduced: With the upgrade to a newer version of Matomo, we always update the versions of the free and premium plugins. There are no updates to the free plugins, just the preimum plugins. How these changes are implemented: * Store the new unzipped plugin packages in this repository * Update the Dockerfile to copy in the content from the new versions of the plugins. Related Jira tickets: * https://mitlibraries.atlassian.net/browse/INFRA-656
Why these changes are being introduced: As part of our planned maintenance for ECS-based applications, we are explicitly declaring the CPU Architecture for the task. This update to the application must be handled with tight coordination with changes to the infrastructure repository. See commit b2903e88 on mitlib-tf-workloads-matomo for the corresponding infrastructure update. How this addresses that need: * Add the .aws-architecture file to declare the CPU architecture * Update .gitignore to ignore the .arch_tag file * Update the Makefile with the new build and deploy commands for Dev1 Side effects of this change: This must be done together with changes to the task definition. If not, this will break the task.
cabutlermit
marked this pull request as ready for review
August 5, 2026 14:53
dhrutibc
approved these changes
Aug 5, 2026
dhrutibc
left a comment
dhrutibc
left a comment
There was a problem hiding this comment.
Looks good - Matomo and all plugin versions are correct
tim-rix
approved these changes
Aug 5, 2026
tim-rix
left a comment
tim-rix
left a comment
Contributor
There was a problem hiding this comment.
Everything looks OK to me.
I didn't review the plugin changes. Those files are expected to change and are from outside sources, not written for this repo.
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
3 participants
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.
What does this PR do?
aws-architecturefile to explicitly set the CPU Architecture for the containerMakefileto use the architecture-specificdist-devandpublic-devcommands that expect the.aws-architecturefileHelpful background context
The infrastructure changes related to CPU architecture must be deployed to the AWS Account immediately prior to the triggered GitHub Actions run from this repository. For Dev1, this was done manually via a commit to the
devbranch on the infrastructure repository followed by amake publish-devrun from this repository.For Stage-Workloads and Prod-Workloads, we will need to actively manage the opening of PRs and the merging of branches to ensure that this works smoothly. As a reminder,
stagebranchHow can a reviewer manually see the effects of these changes?
To see the changes, log in to the dev-matomo instance and verify the Matomo version and the versions of all of the plugins.
Includes new or updated dependencies?
YES: See PR#39 on mitlib-tf-workloads-matomo
What are the relevant tickets?
Developer
Code Reviewer
(not just this pull request message)