![Introducing Enhanced Alert Actions and Triage Functionality](https://cdn.sanity.io/images/cgdhsj6q/production/fe71306d515f85de6139b46745ea7180362324f0-2530x946.png?w=800&fit=max&auto=format)
Product
Introducing Enhanced Alert Actions and Triage Functionality
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
@hashicorp/mktg-global-styles
Advanced tools
Readme
Global styles used across HashiCorp sites.
The primary import is style.css
, which contains a few important styles:
.g-grid
class which is our standard grid layout setup (src).g-grid-container
class which is our standard content container (src)Each of these can be imported individually, but this is not recommended. They are separated for internal organization rather than external consumption
This package is severely out of date and generally needs a lot of additional work, most of which will be breaking. A short list of what needs to change follows:
code-highlighting.css
is no longer used, instead code highlighting styles are imported from @hashicorp/nextjs-scripts
temporary-to-remove
files need to be evaluated and culledglobal
imports our color variables, it does not need to be imported in any other file, or it will be doubled. these imports are relics from when we compiled variables rather than using them as-isglobal
file needs to be broken apart into pieces and assembled within style.css
Publishing is handled through the changesets
library. Publishing is done in CI if changes are found. For more information on how to work with changesets, see this document.
Run the following command and follow the prompt:
npx changeset
To make any adjustments to your changeset, just edit the file!
The release process is handled mostly automatically via the changesets GitHub action. When changeset files get merged to main
, a Pull Request is opened which will, upon merge, release all pending changesets and remove the changeset files. We should not need to publish manually with this flow. See the changesets/action
(https://github.com/changesets/action) repo for more information.
If you want to test your changes before merging, you can add a release:canary
label to your pull request. If any changeset files are found, a release will be created and tagged with canary
. You can then install the canary version elsewhere:
npm install @hashicorp/mktg-global-styles@canary
Prereleases are also handled through a process integrated into changesets
. The full flow is outlined in this document. To enter a prerelease mode for the canary
tag, we would do something like this:
npx changeset pre enter canary
GITHUB_TOKEN=<your token> npx changeset version
GITHUB_TOKEN=<your token> npx changeset publish
To continue publishing preleases, use the npx changeset
command like normal and use the version
and publish
commands as appropriate.
FAQs
global styles shared across HashiCorp sites
The npm package @hashicorp/mktg-global-styles receives a total of 3,338 weekly downloads. As such, @hashicorp/mktg-global-styles popularity was classified as popular.
We found that @hashicorp/mktg-global-styles demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 30 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Socket now supports four distinct alert actions instead of the previous two, and alert triaging allows users to override the actions taken for all individual alerts.
Security News
Polyfill.io has been serving malware for months via its CDN, after the project's open source maintainer sold the service to a company based in China.
Security News
OpenSSF is warning open source maintainers to stay vigilant against reputation farming on GitHub, where users artificially inflate their status by manipulating interactions on closed issues and PRs.