Skip to main content

Updates 30 July, 2024

· 2 min read
Zen Voich
Zen Voich
Mops Maintainer

Summary​

  • First Mops blog post
  • Common nav bar
  • Mops CLI updates
  • GitHub Action update
  • Documentation updates
  • GitHub dependency name restrictions

Mops blog​

(by @ZenVoich)

This is the first blog post of the new Mops blog.

Further Mops updates will be posted here. Previous updates can be found in the Dfinity forum.

Common nav bar​

(by @ZenVoich)

Added a common nav bar to all subdomains for easier navigation.

Mops CLI updates​

0.45.0 by @ZenVoich

  • Updated npm dependencies
  • Added --no-install flag to mops sources command
  • Added --verbose flag to mops publish command
  • Added support for dependency version pinning
  • Suppress hashing tool detecting error in moc-wrapper.sh on Linux
  • Fixed moc-wrapper error when no .mops folder exists
  • Fixed cache folder delete on github install error

GitHub Action update​

(by @ZenVoich)

New version 1.3.1 of setup-mops action is released.

The action is updated to use the on-chain storage to install Mops, which gave a 2x speedup to the installation process (from ~20s to ~10s).

If you are using the action in this way:

- uses: ZenVoich/setup-mops@v1

no changes are required from your side.

Documentation updates​

(by @ZenVoich)

GitHub dependency name restrictions​

(by @ZenVoich)

Now you cannot publish a package with a github dependency whose name is already taken in the Mops registry.

This helps to avoid confusion when resolving packages with the same name from different sources, because they can be completely different packages.

Example:

[dependencies]
base = "https://github.com/dfinity/motoko-base#moc-0.12.0" # bad
base_gh_0_12_0 = "https://github.com/dfinity/motoko-base#moc-0.12.0" # ok
any-other-name = "https://github.com/dfinity/motoko-base#moc-0.12.0" # ok