Skip to content

Releases: agriculturegovau/agds-next

February 8th, 2022

08 Feb 04:56
@nathsimpson nathsimpson
2022-02-08
3aabca8
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
February 8th, 2022 Pre-release
Pre-release

⚠️ Note: All releases under the @ag.ds-next package scope should be considered alpha pre-releases. Expect breaking changes. Once we are happy with the state of the core packages we will migrate all packages to @ag.ds.

View the complete release notes on the AG DS website.

"@ag.ds-next/ag-branding": "3.0.0",
"@ag.ds-next/body": "3.0.0",
"@ag.ds-next/box": "3.0.0",
"@ag.ds-next/breadcrumbs": "3.0.0",
"@ag.ds-next/button": "3.0.0",
"@ag.ds-next/card": "1.0.0",
"@ag.ds-next/columns": "2.0.0",
"@ag.ds-next/content": "3.0.0",
"@ag.ds-next/core": "2.0.0",
"@ag.ds-next/footer": "3.0.0",
"@ag.ds-next/header": "3.0.0",
"@ag.ds-next/heading": "3.0.0",
"@ag.ds-next/icon": "3.0.0",
"@ag.ds-next/link-list": "3.0.0",
"@ag.ds-next/main-nav": "3.0.0",
"@ag.ds-next/side-nav": "3.0.0",
"@ag.ds-next/text": "3.0.0"

What's Changed

New Contributors

Full Changelog: https://github.com/steelthreads/agds-next/commits/2022-02-08

Contributors

mikehazell, jordanoverbye, and 2 other contributors
Loading

January 24th, 2022

24 Jan 06:50
@nathsimpson nathsimpson
2022-01-24
60b9a8d
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
January 24th, 2022 Pre-release
Pre-release

Add lots of new components!

  • Breadcrumbs
  • Icon
  • SideNav

⚠️ Note: All releases under the @ag.ds-next package scope should be considered alpha pre-releases. Expect breaking changes. Once we are happy with the state of the core packages we will migrate all packages to @ag.ds.

View the complete release notes on the AG DS website.

"@ag.ds-next/ag-branding": "2.0.0",
"@ag.ds-next/body": "2.0.0",
"@ag.ds-next/box": "2.0.0",
"@ag.ds-next/breadcrumbs": "2.0.1",
"@ag.ds-next/button": "2.0.0",
"@ag.ds-next/content": "2.0.0",
"@ag.ds-next/core": "1.1.0",
"@ag.ds-next/footer": "2.0.0",
"@ag.ds-next/header": "2.0.0",
"@ag.ds-next/heading": "2.0.0",
"@ag.ds-next/icon": "2.0.1",
"@ag.ds-next/link-list": "2.0.0",
"@ag.ds-next/main-nav": "2.0.0",
"@ag.ds-next/side-nav": "2.0.0",
"@ag.ds-next/text": "2.0.0",
"@ag.ds-next/text-link": "2.0.0",

What's Changed

New Contributors

Full Changelog: https://github.com/steelthreads/agds-next/commits/2022-01-24

Contributors

mikehazell, jordanoverbye, and nathsimpson
Loading

⚙️ January 7th, 2022

07 Jan 09:47
@mikehazell mikehazell
2022-01-07
70c87ec
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
⚙️ January 7th, 2022 Pre-release
Pre-release

Changes to imporve usability of primitive components and to better enable using framework provided link components.

  • Body: Applied fontGrid to some content elements
  • Core, LinkList, MainNav: Add a linkComponent to Core which can be used in LinkList and MainNav. This enables supporting Link components from next.js or react-router inside DS components.
  • Box: Added flexGrow and flexShrink props

⚠️ Note: All releases under the @ag.ds-next package scope should be considered alpha pre-releases. Expect breaking changes. Once we are happy with the state of the core packages we will migrate all packages to @ag.ds.

View the complete release notes on the AG DS website.

"@ag.ds-next/ag-branding": "1.0.1",
"@ag.ds-next/body": "1.0.1",
"@ag.ds-next/box": "1.0.1",
"@ag.ds-next/button": "1.0.1",
"@ag.ds-next/content": "1.0.1",
"@ag.ds-next/core": "1.0.1",
"@ag.ds-next/footer": "1.0.1",
"@ag.ds-next/header": "1.0.1",
"@ag.ds-next/heading": "1.0.1",
"@ag.ds-next/link-list": "1.0.1",
"@ag.ds-next/main-nav": "1.0.1",
"@ag.ds-next/text": "1.0.1",
"@ag.ds-next/text-link": "1.0.1",

Changelog

Aside from the complete release notes on the @ag.ds-next website, you can also view the verbose change log in the related PR (#29) for this release.

View verbose release notes

Releases

@ag.ds-next/[email protected]

Patch Changes

@ag.ds-next/[email protected]

Patch Changes

@ag.ds-next/[email protected]

Patch Changes

@ag.ds-next/[email protected]

Patch Changes

@ag.ds-next/[email protected]

Patch Changes

@ag.ds-next/[email protected]

Patch Changes

  • 458f1db: Add a linkComponent to Core which can be used in LinkList and MainNav. This enables supporting Link components from next.js or react-router inside DS components.

@ag.ds-next/[email protected]

Patch Changes

@ag.ds-next/[email protected]

Patch Changes

@ag.ds-next/[email protected]

Patch Changes

@ag.ds-next/[email protected]

Patch Changes

@ag.ds-next/[email protected]

Patch Changes

  • 458f1db: Add a linkComponent to Core which can be used in LinkList and MainNav. This enables supporting Link components from next.js or react-router inside DS components.
  • Updated dependencies [458f1db]
  • Updated dependencies [458f1db]

@ag.ds-next/[email protected]

Patch Changes

@ag.ds-next/[email protected]

Patch Changes

@ag.ds-next/[email protected]

Patch Changes

@ag.ds-next/[email protected]

Patch Changes

Loading

✨ January 5th, 2022

07 Jan 08:04
@mikehazell mikehazell
2022-01-05
6a2d93e
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
✨ January 5th, 2022 Pre-release
Pre-release

Initial release. This is the first release of the upcoming Agriculture Design-System components.

⚠️ Note: All releases under the @ag.ds-next package scope should be considered alpha pre-releases. Expect breaking changes.
Once we are happy with the state of the core packages we will migrate all packages to @ag.ds.

This release contains the base set of core and primitive components (core, box, text etc.) as well as the first iteration of standard layout components like header, footer and nav.

View the complete release notes on the AG DS website.

"@ag.ds-next/ag-branding": "1.0.0",
"@ag.ds-next/body": "1.0.0",
"@ag.ds-next/box": "1.0.0",
"@ag.ds-next/button": "1.0.0",
"@ag.ds-next/content": "1.0.0",
"@ag.ds-next/core": "1.0.0",
"@ag.ds-next/footer": "1.0.0",
"@ag.ds-next/header": "1.0.0",
"@ag.ds-next/heading": "1.0.0",
"@ag.ds-next/link-list": "1.0.0",
"@ag.ds-next/main-nav": "1.0.0",
"@ag.ds-next/text-link": "1.0.0",
"@ag.ds-next/text": "1.0.0",

Changelog

Aside from the complete release notes on the @ag.ds-next website. You can also view the verbose change log in the related PR (#24) for this release.

View verbose release notes

Releases

@ag.ds-next/[email protected]

Major Changes

  • 7e4600a: Initial Test Release

    This is the initial pre-release of the base set of DS components. The goal of this release is to test the process. Expect things to be broken if you're trying to use components from this release.

    If this is just a test, why is it a "major release"

    TL;DR: Because it is a major release. Before there was nothing. Now there is something.

    The slightly more complete answer is that publishing anything below a 1.0.0 to npm can lead to some unexpected behaviour when it comes to resolving dependencies. These numbers only have meaning within a given context so there is little benefit to using 0.1.0 over 1.0.0 other than that it hints to users that this may not be stable. Just starting at 1.0.0 makes things easier.

Patch Changes

@ag.ds-next/[email protected]

Major Changes

  • 7e4600a: Initial Test Release

    This is the initial pre-release of the base set of DS components. The goal of this release is to test the process. Expect things to be broken if you're trying to use components from this release.

    If this is just a test, why is it a "major release"

    TL;DR: Because it is a major release. Before there was nothing. Now there is something.

    The slightly more complete answer is that publishing anything below a 1.0.0 to npm can lead to some unexpected behaviour when it comes to resolving dependencies. These numbers only have meaning within a given context so there is little benefit to using 0.1.0 over 1.0.0 other than that it hints to users that this may not be stable. Just starting at 1.0.0 makes things easier.

Patch Changes

@ag.ds-next/[email protected]

Major Changes

  • 7e4600a: Initial Test Release

    This is the initial pre-release of the base set of DS components. The goal of this release is to test the process. Expect things to be broken if you're trying to use components from this release.

    If this is just a test, why is it a "major release"

    TL;DR: Because it is a major release. Before there was nothing. Now there is something.

    The slightly more complete answer is that publishing anything below a 1.0.0 to npm can lead to some unexpected behaviour when it comes to resolving dependencies. These numbers only have meaning within a given context so there is little benefit to using 0.1.0 over 1.0.0 other than that it hints to users that this may not be stable. Just starting at 1.0.0 makes things easier.

Patch Changes

@ag.ds-next/[email protected]

Major Changes

  • 7e4600a: Initial Test Release

    This is the initial pre-release of the base set of DS components. The goal of this release is to test the process. Expect things to be broken if you're trying to use components from this release.

    If this is just a test, why is it a "major release"

    TL;DR: Because it is a major release. Before there was nothing. Now there is something.

    The slightly more complete answer is that publishing anything below a 1.0.0 to npm can lead to some unexpected behaviour when it comes to resolving dependencies. These numbers only have meaning within a given context so there is little benefit to using 0.1.0 over 1.0.0 other than that it hints to users that this may not be stable. Just starting at 1.0.0 makes things easier.

Patch Changes

@ag.ds-next/[email protected]

Major Changes

  • 7e4600a: Initial Test Release

    This is the initial pre-release of the base set of DS components. The goal of this release is to test the process. Expect things to be broken if you're trying to use components from this release.

    If this is just a test, why is it a "major release"

    TL;DR: Because it is a major release. Before there was nothing. Now there is something.

    The slightly more complete answer is that publishing anything below a 1.0.0 to npm can lead to some unexpected behaviour when it comes to resolving dependencies. These numbers only have meaning within a given context so there is little benefit to using 0.1.0 over 1.0.0 other than that it hints to users that this may not be stable. Just starting at 1.0.0 makes things easier.

Patch Changes

@ag.ds-next/[email protected]

Major Changes

  • 7e4600a: Initial Test Release

    This is the initial pre-release of the base set of DS components. The goal of this release is to test the process. Expect things to be broken if you're trying to use components from this release.

    If this is just a test, why is it a "major release"

    TL;DR: Because it is a major release. Before there was nothing. Now there is something.

    The slightly more complete answer is that publishing anything below a 1.0.0 to npm can lead to some unexpected behaviour when it comes to resolving dependencies. These numbers only have meaning within a given context so there is little benefit to using 0.1.0 over 1.0.0 other than that it hints to users that this may not be stable. Just starting at 1.0.0 makes things easier.

@ag.ds-next/[email protected]

Major Changes

  • 7e4600a: Initial Test Release

    This is the initial pre-release of the base set of DS components. The goal of this release is to test the process. Expect things to be broken if you're trying to use components from this release.

    If this is just a test, why is it a "major release"

    TL;DR: Because it is a major release. Before there was nothing. Now there is something.

    The slightly more complete answer is that publishing anything below a 1.0.0 to npm can lead to some unexpected behaviour when it comes to resolving dependencies. These numbers only have meaning within a given context so there is little benefit to using 0.1.0 over 1.0.0 other than that it hints to users that this may not be stable. Just starting at 1.0.0 makes things easier.

Patch Changes

@ag.ds-next/[email protected]

Major Changes

  • 7e4600a: Initial Test Release

    This is the initial pre-release of the base set of DS components. The goal of this release is to test the process. Expect things to be broken if you're trying to use components from this release.

    If this is just a test, why is it a "major release"

    TL;DR: Because it is a major release. Before there was nothing. Now there is something.

    The slightly more complete answer is that publishing anything below a 1.0.0 to npm can lead to some unexpected behaviour when it comes to resolving dependencies. These numbers only have meaning within a given context so there is little benefit to using 0.1.0 over 1.0.0 other than that it hints to users that this may not be stable. Just starting at 1.0.0 makes things easier.

Patch Changes

@ag.ds-next/[email protected]

Major Changes

  • 7e4600a: Initial Test Release

    This is the initial pre-release of the base set of DS components. The goal of this release is to test the process. Expect things to be broken if you're trying to use components from this release.

    If this is just a test, why is it a "major release"

    TL;DR: Because it is a major release. Before there was nothing. Now there is something.

    The slightly more complete answer is that publishing anything below a 1.0.0 to npm can lead to some unexpected behaviour when it comes to resolving dependencies. These numbers only have meaning within a given context so there is little benefit to using 0.1.0 over 1.0.0 other than that it hints to users that this may not be stable. Just starting at 1.0.0 makes things...

Read more
Loading