search

stanford-oval / genie-server

The home server version of Almond
Apache License 2.0
266 stars 42 forks source link

Bump @js-temporal/polyfill from 0.2.0 to 0.4.0 #330

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps @js-temporal/polyfill from 0.2.0 to 0.4.0.

Release notes

Sourced from @​js-temporal/polyfill's releases.

Version 0.4.0

Please see CHANGELOG.md for a summary of changes in this release.

Thanks to everyone who contributed to this release!

Version 0.3.0

Please see CHANGELOG.md for a summary of changes in this release.

Thanks to everyone who contributed to this release!

Changelog

Sourced from @​js-temporal/polyfill's changelog.

0.4.0

This version roughly corresponds with all the changes made to the Temporal polyfill as of the January 2022 TC39 Plenary meeting.

Breaking changes:

  • Use JSBI instead of big-integer for Big Integer math operations. If your codebase does not need to polyfill BigInt, consider using the JSBI Babel plugin to transpile these operations to native BigInt.
  • Reject plain date-only strings ([b733c213], see also Spec PR, proposal-temporal polyfill PR)
  • Reject '-000000' as an extended year value ([670cda6b], see also Spec PR)
  • Add missing branding checks for Calendar and Timezone classes to match spec changes ([670cda6b], see also Spec PR)

Bug fixes:

Non-breaking changes:

  • Rename public ...FromFields types ([3554d7f1])
  • Add validation for hard-coded Era data in Calendar.ts ([08e84c9f])
  • Improve code in Calendar.ts to handle calendar with a constant era but a variable number of months in a year ([ef8c588b])
  • Add an optional calendar to PlainTime, PlainDateTime, and PlainMonthDay ([f8837367], see also Spec PR)
  • Only require a year in Gregorian calendar implementations, not a full date ([02aec1c3])
  • Include valueOf in the Temporal.Duration type ([b1dd7eb3])
  • Expand the types allowed to be used as TimezoneLike and CalendarLike to match the spec ([9d54c646])
  • Improve worse-case performance when finding Timezone transition points by over 1000X! ([e70d6324])
  • Change Calendar.fields to return an Array, not an Iterable ([3145c6c4], see also Spec PR)

Other:

  • Update build dependencies ([500b4c97])
  • Run tests against Node 17 on CI ([db63e22a])

0.3.0

This version roughly corresponds with all the changes made to the Temporal polyfill as of the October 2021 TC39 Plenary meeting.

Breaking changes:

  • Timezones now require a getOffsetNanosecondsFor method, and no longer fall back to the intrinsic definition (previously provided by Temporal.Timezone#getOffsetNanosecondsFor) if not provided. ([08346dc5], see also proposal-temporal polyfill PR)
  • Disallow Z designators when parsing strings for Plain Temporal types ([f3f8a994], see also Spec PR)
  • Allow ISO strings with "Z" + a bracketed IANA name ([70bd9898], see also Spec PR)
  • Emit ES2020 builds for newer browsers, and emit ES5 for older browsers. ([2331468d], [9e95c62b])
  • Temporal.Duration constructor will now throw if given a non-integer ([9df5d068], see also Spec PR)
  • Remove support for sub-minute offsets in ISO strings ([766e5037], see also Spec PR, Spec PR)
  • Throw TypeError on missing options from Duration.total ([4ec075f0], see also Spec PR)
  • Reject non-integer Duration fields in Duration.with() ([e6b2488d], see also Spec PR)

... (truncated)

Commits
  • 5df9d9f Release v0.4.0. (#143)
  • 670cda6 Port recent changes from tc39/proposal-temporal. (#142)
  • 3145c6c Fix Calendar.fields return type to match the spec
  • f2e2658 Fix Node16 tests (port proposal-temporal/#2064)
  • 281684c Fix Node14 tests broken by ICU update
  • e70d632 Fix TimeZone.p.getXxxTransition() worst-case perf
  • 21272b2 Restore comment about chromium issue
  • 62639c8 parseFromEnUsFormat throws on unexpected input
  • 2abeec5 tests for parseFromEnUsFormat
  • 6e95746 move parsing out of GetFormatterParts
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by jameswr, a new releaser for @​js-temporal/polyfill since your current version.


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 2 years ago

Superseded by #331.