Skip to content

Latest commit

 

History

History
906 lines (416 loc) · 51.5 KB

RELEASE_NOTES.md

File metadata and controls

906 lines (416 loc) · 51.5 KB

RELEASE NOTES

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to a flavor of Semantic Versioning which includes Scopes and Epochs.

Quick Navigation

Scope Current Release Commit Count
ActiveElement 0.2.0 1 commits
Audio 0.1.1 5 commits
AutoFocus 0.1.1 7 commits
Bounds 0.2.1 6 commits
BroadcastChannel 0.2.1 6 commits
Clipboard 0.2.1 6 commits
Common 0.1.1 5 commits
Devices 0.1.1 5 commits
EventBus 0.2.1 6 commits
EventListener 0.1.1 5 commits
Idle 0.2.1 6 commits
Keyboard 0.2.1 6 commits
Media 0.2.1 6 commits
Mouse 0.2.1 8 commits
Permission 0.2.0 1 commits
Primitives 0.5.0 12 commits
Raf 0.2.1 6 commits
Rootless 0.2.0 1 commits
Scheduled 0.2.1 6 commits
Scroll 0.2.1 6 commits
Spring 0.2.1 7 commits
Storage 0.2.0 1 commits
Timer 0.2.1 8 commits
Trigger 0.2.1 8 commits
Tween 0.2.1 9 commits
InputMask 0.1.0 None yet!
JsxTokenizer 0.1.0 None yet!

ActiveElement

UNRELEASED

Audio

UNRELEASED

0.1.1 - (2025-08-21)

Fixed

Others

AutoFocus

UNRELEASED

0.1.1 - (2025-08-21)

Fixed

Others

Bounds

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

BroadcastChannel

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

Clipboard

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

Common

UNRELEASED

0.1.1 - (2025-08-21)

Fixed

Others

Devices

UNRELEASED

0.1.1 - (2025-08-21)

Fixed

Others

EventBus

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

EventListener

UNRELEASED

0.1.1 - (2025-08-21)

Fixed

Others

Idle

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

Keyboard

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

Media

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

Mouse

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

  • Simplify usage and namespaces (#1) by @cabboose with #120be

  • =MOUSE= REFACTOR: Type signatures now use U4<#HtmlElement, #Element, Document, Window> to better provide accessibility as per the source typings by @cabboose with #36668

  • Add initial project files for Solid-js primitives bindings by @cabboose with #968b5

  • Add CI workflow using Partas.GitNet (#4) by @cabboose with #c3975

  • =MOUSE= HOTFIX: Remove # to prevent compiler type ambiguity by @cabboose with #43f2a

  • =MOUSE= ADDED: Added bindings by @cabboose with #f6dcd

  • fantomas by @shayanhabibi with #a8f38

Permission

UNRELEASED

0.2.0 - (2025-09-25)

Others

Primitives

UNRELEASED

0.5.0 - (2025-09-19)

Others

0.4.0 - (2025-09-19)

Others

0.3.2 - (2025-09-06)

Fixed

0.3.1 - (2025-08-21)

Fixed

Others

Raf

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

Rootless

UNRELEASED

0.2.0 - (2025-09-19)

Others

Scheduled

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

Scroll

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

Spring

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

Storage

UNRELEASED

0.2.0 - (2025-09-25)

Others

Timer

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

Trigger

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

Tween

UNRELEASED

0.2.1 - (2025-08-21)

Fixed

Others

InputMask

No commits at this time.

JsxTokenizer

No commits at this time.

Read more about this SemVer flavor

Epoch Scoped SemVer

This flavor adds an optional marketable value called an EPOCH. There is also an optional disambiguating SCOPE identifier for delineating tags for packages in a mono repo.

The motivation for this is to prevent resistance to utilising SemVer major bumps correctly, by allowing a separate marketable identifier which is easily compatible with the current SemVer spec.

An Epoch/Scope (Sepoch) is an OPTIONAL prefix to a typical SemVer.

  • A Sepoch MUST BE bounded by _ underscores _.
  • The identifiers MUST BE ALPHABETICAL (A-Za-z) identifiers.
  • The Epoch SHOULD BE upper case
  • The Epoch MUST come before the Scope, if both are present.
  • The Scope MUST additionally be bounded by ( parenthesis ).
  • The Scope SHOULD BE capitalised/pascal cased.
  • A Sepoch CAN BE separated from SemVer by a single white space where this is allowed (ie not allowed in git tags).
  • Epoch DOES NOT influence precedence.
  • Scope MUST uniquely identify a single components versioning.
  • Different scopes CANNOT BE compared for precedence.
  • A SemVer without a Scope CAN BE compared to a Scoped SemVer for compatibility. But caution is advised.

There is no enforcement for ordering EPOCHs in this spec, as it would be overly restrictive and yield little value since we can delineate and earlier EPOCH from a later EPOCH by the SemVers.

Example

gitGraph
commit tag: "_ALPS_1.2.3"
branch develop
commit id: "add: ..."
commit
checkout main
cherry-pick id: "add: ..." tag: "_ALPS_2.1.3"
checkout develop
commit
commit
checkout main
merge develop tag: "_ALPS_3.4.5"
checkout develop
commit
commit
checkout main
merge develop tag: "_BRAVO_4.0.0" type: HIGHLIGHT
Loading

While there are breaking changes between versions 1 to 3, we expect that it is less than from 3 to 4. We expect the API surface would change more dramatically, or there is some other significant milestone improvement, in the change from version 3 epoch ALPS to version 4 epoch BRAVO.

_WILDLANDS(Core)_ 4.2.0
_WILDLANDS(Engine)_ 0.5.3
_DELTA(Core)_ 5.0.0
_DELTA(Engine)_ 0.5.3

Cannot be compared to Core versions. Both Engine versions are equal, we can identify that the ecosystems marketed change does not change the Engine packages API