Skip to content

0.0.5 Metadata Stability
Compare
Choose a tag to compare
@MichaelMarner MichaelMarner released this 17 Feb 07:07
· 129 commits to master since this release
v0.0.5
d366e35

0.0.5 has some breaking changes to what the manup.json metadata file should look like. I expect the format will be stable going forward, perhaps with new keys added, but no more breaking changes to what the file should look like.

New Stuff

  • Adds support for the windows platform (yay!)
  • Mostly refactoring code to more easily test

Breaking Changes

Rename to ManUp

We started with the project using Manup in code. However, since that is short for Mandatory Update, the module and service have been renamed to ManUpModule and ManUpService. Strict camel case for the win.

Metadata JSON

Here's a complete example, below are the things that have changed from 0.0.4.

{
    "ios": {
        "minimum": "0.0.1",
        "latest": "1.0.0",
        "url": "http://example.com",
        "enabled": true
    },
    "android": {
        "minimum": "1.0.0",
        "latest": "1.0.0",
        "url": "http://example.com",
        "enabled": true
    },
    "windows": {
        "minimum": "1.0.0",
        "latest": "1.0.0",
        "url": "http://example.com",
        "enabled": false
    }
}

Update URL

The update url now uses the key url instead of link, which is a much better name for describing a URL.

Enabled/Disabled

The app can be enabled or disabled (maintenance mode) on a per platform basis. So, each platform subtree of the metadata has its own enabled key. So, if your Windows version is broken and if you have no intention of fixing it, you can disable it without affecting other users.

Assets 3
Loading