v2.1.0

Changes

• Added loading spinner for log creation (manual and normal) on event page
• Added barcode to device list on reservation page
• Updated documentation

Bug fixes

• Added success message on user creation (previously empty)

Services modified

• newshub-client v2.0.0 -> v2.1.0

Services

• newshub-gateway v2.0.0
• newshub-authentication v2.0.0
• newshub-reservations v2.0.0
• newshub-events v2.0.0
• newshub-files v2.0.0
• newshub-client v2.1.0

v2.0.0

Changes

• Added action logging to reservations microservice
• Removed legacy code from services
• Added image support to user (newshub-authentication) and device (newshub-reservations) models
• Added newshub-files microservice for file uploads

Bug fixes

• Hide microservice ports from host

Services

• newshub-gateway v2.0.0
• newshub-authentication v2.0.0
• newshub-reservations v2.0.0
• newshub-events v2.0.0
• newshub-files v2.0.0
• newshub-client v2.0.0

Notes

NewsHub is skipping directly to v2.0.0 to cleanly break from earlier versioning inconsistencies. With a new monorepo project structure, NewsHub versioning can now be far more consistent. All existing services will begin their versioning at v2.0.0, skipping v1.0.0. Services can continue to be versioned independently from this point and a NewsHub release (as in the cohesive product) will simply be a snapshot of all service versions at a specific point. The monorepo structure allows for this easy cross-service versioning as a single version tag snapshots all of the services at once.

v2.0.0 Alpha

Notes

NewsHub is skipping directly to v2.0.0 to cleanly break from earlier versioning inconsistencies. With a new monorepo project structure, NewsHub versioning can now be far more consistent. All existing services will begin their versioning at v2.0.0, skipping v1.0.0. Services can continue to be versioned independently from this point and a NewsHub release (as in the cohesive product) will simply be a snapshot of all service versions at a specific point. The monorepo structure allows for this easy cross-service versioning as a single version tag snapshots all of the services at once.

For Example:

NewsHub v2.5.0 consists of newshub-authentication v2.3.7, newshub-reservations v2.6.0 etc.