Major Changes
-
029288c: This changes the way
colony-js
clients are typed. We retain only the types of the last 5 versions of the types, all older versions will go untyped. This will give us some breathing room, at least for the amount of extensions that we have now.Furthermore the most recent (upcoming) contract changes were included in ColonyJS.
Some changes were made to fix builds.
-
7e5d60d: The latest update in the ColonyJS series. While most of the changes were done to the internal structure of ColonyJS, this release does include some breaking changes. The bundle-size of ColonyJS was reduced in this release.
Breaking
- All the sub-entrypoints were removed (
extras
,tokens
,events
)- Most of the
extra
s are now in the main entrypoint (@colony/colony-js
) - The
tokens
are now in@colony/tokens
(needs to be installed separately) - The
events
are now in@colony/events
(needs to be installed separately)
- Most of the
getExtensionHash
now takes anExtension
enum value and not a string anymoreimport { getExtensionId, Extension } from "@colony/colony-js"; // When extension is unknown: const extensionHash = getExtensionHash(extensionId as Extension); // Or, to get a hash for a specific extension const extensionHash = getExtensionHash(Extension.VotingReputation);
deployTokenAuthority
on the token client was removed. UsecolonyNetwork.deployTokenAuthority
instead (also for non metatransactions)getTokenInfo
function was removedTokenClientType
is now now also in@colony/tokens
New
- All helper functions and most constants that are used in ColonyJS are now available in
@colony/core
and are also exported from@colony/colony-js
.
Maintenance
- ColonyJS is now a package in the ColonyJS monorepo:
@colony/colony-js
- We are using changesets for versioning now
- The contract build script is now an own package:
@colony/contractor
. The entry in thescripts
section in thepackage.json
was adjusted accordingly. - The contracts are not part of the repository anymore but will always be generated on installation or publishing of the package
- TypeScript settings were upgraded, target is now es2018.
- ColonyJS should now be able to be included in current CJS and ESM projects properly
- All the sub-entrypoints were removed (
Minor Changes
-
3a87d0c:
sdk
getReputation
now returns reputation within a domain as a percentag of the whole reputation within the teamgetReputationPoints
can be used to get the previous behavior- Added an
initialize
function to theVotingReputation
extension
-
83d7828: Add some more exports to the entry point. Now we have
ColonyTokenFactory
(theMetaTxToken
)ColonyFactory
(theIColony
of the latest version)ColonyNetworkFactory
(IColonyNetwork
)
-
0ebb76a: Exported VotingReputationFactory
-
3439729: colony-js gets support for the latest colonyNetwork release hmwss.
Patch Changes
- 8de9d9c: Upgrade TypeDoc to v0.24.8 and adjust link syntax style
- dd5e3c5: Use tsc for compilation in colony-js and sdk
- 415be09: Do not overwrite or delete build files
- 542ffad: Adjust import/export statements to be compatible with ESM only within node.js
- 50eefa9: Improve compatibility between ESM package.json generation and changesets:
- Use template file for package.json stub files (for changeset compatibility)
- Add .js extensions also for type imports and exports
- Add type entries to all package.json files
- Rename all .js config files to .cjs
- Updated dependencies [e931d0e]
- Updated dependencies [245fc59]
- Updated dependencies [8de9d9c]
- Updated dependencies [3a87d0c]
- Updated dependencies [029288c]
- Updated dependencies [c8f5f74]
- Updated dependencies [3439729]
- Updated dependencies [542ffad]
- Updated dependencies [50eefa9]
- @colony/[email protected]
- @colony/[email protected]
- @colony/[email protected]