chore: release hubble 1.11.2 #1841
Conversation
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Wazzymandias
force-pushed
the
chore/release-hubble-1.11.2
branch
from
f3565ae
to
833c46f
Compare
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is an install script?Install scripts are run when the package is installed. The majority of malware in npm is hidden in install scripts. Packages should not be running non-essential scripts during install and there are often solutions to problems people solve with install scripts that can be run at publish time instead. What is protestware?This package is a joke, parody, or includes undocumented or hidden behavior unrelated to its primary function. Consider that consuming this package my come along with functionality unrelated to its primary purpose. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
| @@ -17,6 +17,9 @@ module.exports = { | |||
| // HACK: Allows us to pass arguments in a way recognized by the CLI flag processing library we use | |||
| // This is only necessary when running via PM2. | |||
| args: process.env.HUBBLE_ARGS, | |||
| env: { | |||
| "CATCHUP_SYNC_WITH_SNAPSHOT": process.env.CATCHUP_SYNC_WITH_SNAPSHOT ? (process.env.CATCHUP_SYNC_WITH_SNAPSHOT === "true") : "true", | |||
There was a problem hiding this comment.
We should explicitly set this to false in our deployer so it's not enabled by default for our hubs
Motivation
Change Summary
Describe the changes being made in 1-2 concise sentences.
Merge Checklist
Choose all relevant options below by adding an
xnow or at any time before submitting for reviewAdditional Context
If this is a relatively large or complex change, provide more details here that will help reviewers
PR-Codex overview
This PR updates the version of
@farcaster/hubbleto1.11.2, introduces a fix for catch up sync in the install script, and adds an environment variable for catchup sync with snapshot.Detailed summary
@farcaster/hubbleversion to1.11.2