Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update changesets monorepo (major) - autoclosed #230

Closed
wants to merge 1 commit into from
Closed

Update changesets monorepo (major) - autoclosed #230

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 6, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@capsizecss/core (source) ^3.0.0 -> ^4.0.0 age adoption passing confidence dependencies major
actions/cache v3.0.2 -> v4.0.2 age adoption passing confidence action major
actions/checkout v3 -> v4 age adoption passing confidence action major
actions/setup-node v3.1.1 -> v4.0.3 age adoption passing confidence action major
eslint (source) 8.56.0 -> 9.9.1 age adoption passing confidence devDependencies major
husky 4.3.x -> 9.1.x age adoption passing confidence devDependencies major
vitest (source) 1.5.0 -> 2.0.5 age adoption passing confidence devDependencies major

Release Notes

seek-oss/capsize (@​capsizecss/core)

v4.1.2

Compare Source

Patch Changes

  • #​200 6238501 Thanks @​michaeltaranto! - createFontStack: Prefer postscriptName or fullName for fallback source

    The @font-face declaration aliases generated by createFontStack now favour postscriptName and fullName over familyName from the provided metrics when selecting a local font face as a fallback.

    MDN recommends using either fullName and postscriptName when accessing local fonts to ensure the best matching across platforms, while also enabling selection of a single font face within a larger family, e.g. Arial Bold or Arial-BoldMT within Arial.
    For details see MDN.

    ⚠️ Note: Falling back to familyName (original behaviour) makes this work backwards compatible with older versions of font metrics.

v4.1.1

Compare Source

Patch Changes

  • #​198 f55acae Thanks @​michaeltaranto! - createFontStack: Apply line-gap-override with no lineGap in preferred font

    Ensure that the line-gap-override property is applied correctly when overriding a fallback font with a web font that has no lineGap.
    Previously if the override was zero it would be omitted from the declaration, rather than the correct behaviour of overriding the fallback metric to zero.

  • #​199 630a5fe Thanks @​michaeltaranto! - createFontStack: Ensure provided `size-adjust` is factored into metric overrides

    Ensures a custom size-adjust value provided via the fontFaceProperties option is factored into the calculations for the metric overrides.

Example

If a custom size-adjust value is provided:

createFontStack([merriweatherSans, arial], {
  fontFaceProperties: {
    sizeAdjust: '300%',
  },
});

The resulting metric overrides are now adjusted accordingly:

 @​font-face {
   font-family: "Merriweather Sans Fallback";
   src: local('Arial');
-  ascent-override: 92.3409%;
+  ascent-override: 32.8%;
-  descent-override: 25.619%;
+  descent-override: 9.1%;
   line-gap-override: 0%;
   size-adjust: 300%;
 }

v4.1.0

Compare Source

Minor Changes

  • #​177 879208b Thanks @​michaeltaranto! - xWidthAvg: Add subset support for non-latin character sets

    Previously the xWidthAvg metric was calculated based on the character frequency as measured from English text only.
    This resulted in the xWidthAvg metric being incorrect for languages that use a different unicode subset range, e.g. Thai.

    Supporting Thai now enables adding support for other unicode ranges in the future.

What's changed?
@capsizecss/metrics

The subsets field has been added to the metrics object, providing the xWidthAvg metric for each subset — calculated against the relevant character frequency data.

 {
   "familyName": "Abril Fatface",
   ...
+  "subsets": {
+    "latin": {
+      "xWidthAvg": 512
+    },
+    "thai": {
+      "xWidthAvg": 200
+    }
+  }
 }

There are no changes to any of the other existing metrics.

@capsizecss/core

Fallback font stacks can now be generated per subset, allowing the correct xWidthAvg metric to be used for the relevant subset.

The createFontStack API now accepts subset as an option:

const { fontFamily, fontFaces } = createFontStack([lobster, arial], {
  subset: 'thai',
});

v4.0.0

Compare Source

Major Changes

  • #​168 8819ff1 Thanks @​mrm007! - Precompile Capsize packages with Crackle

    Migrating Capsize packages to be precompiled with Crackle, with a key change being Crackle now handles entry points instead of Preconstruct.

    Other benefits include:

    • Modern module entry point syntax using the "exports" field with better tooling compatibility.
    • Improved types and better ESM and CJS compatibility
    • Better alignment between compiled code and module entry points
BREAKING CHANGES:
API changes

While technically a breaking change, consumers of Capsize's public APIs are not affected by this change.
If you are affected due to reaching into package internals, please get in touch and see if we can find a more maintainable approach.

TypeScript

TypeScript consumers should ensure they are using a compatible [moduleResolution strategy in TSConfig][moduleResolution strategy in TSConfig] — either node16, nodenext or bundler. This will ensure types are correctly resolved across the different module specifications.

Patch Changes

  • #​164 a308885 Thanks @​michaeltaranto! - createFontStack: Append original fallback font name to the font stack

    The fontFamily returned from createFontStack now includes the original fallback font name(s). These are appended to the end of the font stack in the case the preferred font and generated fallbacks are not available.

    import lobster from '@​capsizecss/metrics/lobster';
import arial from '@​capsizecss/metrics/arial';

const { fontFamily } = createFontStack([lobster, arial]);

    Where fontFamily is now:

    - `Lobster, 'Lobster Fallback: Arial'`
+ `Lobster, 'Lobster Fallback: Arial', Arial`

  • #​164 a308885 Thanks @​michaeltaranto! - createFontStack: Quote font-family in @font-face declaration if needed

    Previously, when using fontFaceFormat: 'styleObject', the generated fallback name was not quoted as necessary within the @font-face declaration.
    This could cause issues if the font family name contained spaces or other characters that required quoting.

actions/cache (actions/cache)

v4.0.2

Compare Source

v4.0.1

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v4...v4.0.1

v4.0.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v4.0.0

v3.3.3

Compare Source

What's Changed

New Contributors

Full Changelog: actions/cache@v3...v3.3.3

v3.3.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.3.2

v3.3.1

Compare Source

What's Changed

Full Changelog: actions/cache@v3...v3.3.1

v3.3.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.3.0

v3.2.6

Compare Source

What's Changed

Full Changelog: actions/cache@v3...v3.2.6

v3.2.5

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.2.5

v3.2.4

Compare Source

What's Changed

New Contributors

Full Changelog: actions/cache@v3...v3.2.4

v3.2.3

Compare Source

What's Changed

New Contributors

Full Changelog: actions/cache@v3...v3.2.3

v3.2.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3.2.1...v3.2.2

v3.2.1

Compare Source

What's Changed

Full Changelog: actions/cache@v3.2.0...v3.2.1

v3.2.0

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.2.0

v3.0.11

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.0.11

v3.0.10

Compare Source

  • Fix a bug with sorting inputs.
  • Update definition for restore-keys in README.md

v3.0.9

Compare Source

  • Enhanced the warning message for cache unavailability in case of GHES.

v3.0.8

Compare Source

What's Changed

  • Fix zstd not working for windows on gnu tar in issues.
  • Allow users to provide a custom timeout as input for aborting cache segment download using the environment variable SEGMENT_DOWNLOAD_TIMEOUT_MIN. Default is 60 minutes.

v3.0.7

Compare Source

What's Changed

  • Fix for the download stuck problem has been added in actions/cache for users who were intermittently facing the issue. As part of this fix, new timeout has been introduced in the download step to stop the download if it doesn't complete within an hour and run the rest of the workflow without erroring out.

v3.0.6

Compare Source

What's Changed
New Contributors

Full Changelog: actions/cache@v3...v3.0.6

v3.0.5

Compare Source

Removed error handling by consuming actions/cache 3.0 toolkit, Now cache server error handling will be done by toolkit.

v3.0.4

Compare Source

In this release, we have fixed the tar creation error while trying to create it with path as ~/ home folder on ubuntu-latest.

v3.0.3

Compare Source

Fixed avoiding empty cache save when no files are available for caching. (https://github.com/actions/cache/issues/624)

actions/checkout (actions/checkout)

v4

Compare Source

actions/setup-node (actions/setup-node)

v4.0.3

Compare Source

v4.0.2

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-node@v4.0.1...v4.0.2

v4.0.1

Compare Source

What's Changed
New Contributors

Full Changelog: actions/setup-node@v4...v4.0.1

v4.0.0

Compare Source

What's Changed

In scope of this release we changed version of node runtime for action from node16 to node20 and updated dependencies in https://github.com/actions/setup-node/pull/866

Besides, release contains such changes as:

New Contributors

Full Changelog: actions/setup-node@v3...v4.0.0

v3.8.2

Compare Source

What's Changed

Full Changelog: actions/setup-node@v3...v3.8.2

v3.8.1

Compare Source

What's Changed

In scope of this release, the filter was removed within the cache-save step by @​dmitry-shibanov in https://github.com/actions/setup-node/pull/831. It is filtered and checked in the toolkit/cache library.

Full Changelog: actions/setup-node@v3...v3.8.1

v3.8.0

Compare Source

What's Changed
Bug fixes:
Feature implementations:
Documentation changes:
Update dependencies:
New Contributors

Full Changelog: actions/setup-node@v3...v3.8.0

v3.7.0

Compare Source

What's Changed

In scope of this release we added a logic to save an additional cache path for yarn 3 (related pull request and feature request). Moreover, we added functionality to use all the sub directories derived from cache-dependency-path input and add detect all dependencies directories to cache (related pull request and feature request).

Besides, we made such changes as:

New Contributors

Full Changelog: actions/setup-node@v3...v3.7.0

v3.6.0: Add Support for Nightly, Canary and RC builds for Node.js

Compare Source

In scope of this release we added support to download nightly, rc (https://github.com/actions/setup-node/pull/611) and canary (https://github.com/actions/setup-node/pull/619) Node.js distributions.

For nightly versions:
jobs:
  build:
    runs-on: ubuntu-latest
    name: Node sample
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '16-nightly'
      - run: npm ci
      - run: npm test
For canary versions:
jobs:
  build:
    runs-on: ubuntu-latest
    name: Node sample
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '16-v8-canary’
      - run: npm ci
      - run: npm test
For rc versions:
jobs:
  build:
    runs-on: ubuntu-latest
    name: Node sample
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '16.0.0-rc.1’
      - run: npm ci
      - run: npm test

Note: For more examples please refer to documentation.

Besides, we added the following changes as:

v3.5.1: Update @​actions/core and Print Node, Npm, Yarn versions

Compare Source

In scope of this release we updated actions/core to 1.10.0. Moreover, we added logic to print Nodejs, Npm, Yarn versions after installation.

v3.5.0: Add support for engines.node and Volta

Compare Source

In scope of this release we add support for engines.node. The action will be able to grab the version form package.json#engines.node. https://github.com/actions/setup-node/pull/485. Moreover, we added support for Volta

Besides, we updated @​actions/core to 1.9.1 and @​actions/cache to 3.0.4

v3.4.1: Fix pnpm output and node-version output issues

Compare Source

In scope of this release we fixed bugs related to the pnpm 7.5.1 output issue from pnpm store path https://github.com/actions/setup-node/pull/545. Moreover we fixed the issue with falling on node-version output https://github.com/actions/setup-node/pull/540.

v3.4.0: Add support for asdf format and update actions/cache version to 3.0.0

Compare Source

In scope of this release we

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@changeset-bot changeset-bot
Copy link

changeset-bot bot commented Aug 6, 2024 •
edited
Loading

⚠️ No Changeset found

Latest commit: d060711

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@renovate renovate bot force-pushed the renovate/major-changesets-monorepo branch from 445d338 to dbed480 Compare August 10, 2024 05:50
@renovate renovate bot force-pushed the renovate/major-changesets-monorepo branch from dbed480 to d060711 Compare August 24, 2024 17:57
@renovate renovate bot changed the title Update changesets monorepo (major) Update changesets monorepo (major) - autoclosed Sep 3, 2024
@renovate renovate bot closed this Sep 3, 2024
@renovate renovate bot deleted the renovate/major-changesets-monorepo branch September 3, 2024 05:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants