This is a report only repository for the online entreprenuer operations and documentation software eHUB. This means no code is hosted here and the main purpose is to enable users of eHUB to report issues they find in the software as well submit ideas for improvement. This should be done as an issue, from the issues tab.
Issues are like tickets, and do not only cover problems/bugs as the naming implies. Also improvements and refactors are covered as issues, and will be found in the issue list.
You can always ask questions through the contact form on our webpage.
When a release is published, a workflow finds the latest matching production or pre-release for the same major and minor version in each eHUB component repository, asks GitHub Copilot CLI to create Swedish user-facing documentation, and updates the release notes.
The workflow uses the built-in GITHUB_TOKEN, with separate least-privilege permissions for generating documentation and updating a release. In the Studio 27 organization settings, enable Allow use of Copilot CLI billed to the organization under the GitHub Copilot CLI policy. No additional token is needed for Copilot CLI.
The workflow reads public component repositories without an additional token. If any component repository is private, add a fine-grained personal access token as the SUBREPO_READ_TOKEN Actions secret in this repository, granting it Contents: read access to all three component repositories.
Create the token with studio27se as the resource owner and select ehub-backend-api, ehub-webapp, and ehub-app-ionic. Obtain organization approval if required, then save it under Settings → Secrets and variables → Actions → New repository secret as SUBREPO_READ_TOKEN. An organization secret must grant access to this ehub repository. The built-in GITHUB_TOKEN is scoped to this repository and cannot read private component repositories.
If generate reports HTTP 404 while fetching component releases, check that this secret is set, the token has not expired, and it has access to the named repository. GitHub returns 404 for inaccessible private repositories as well as nonexistent ones; this is not treated as “no changes.” After correcting the secret, re-run the failed workflow. The component-read token is not passed to Copilot CLI.
This section outlines the upcoming release dates for eHUB as holistic system.
- Frequency: Releases are planned on a fortnight basis.
- Release Days: Thursday, typically at 09.00pm CET.
- Major Releases: Introduce significant new features or changes. Indicated by increase in the first number of the version. (e.g., v3.0.0)
- Minor Releases: Add enhancements or smaller features. Indicated by increase of the second number of the version. (e.g., v2.12.0)
- Patch Releases: Focus on bug fixes or urgent updates. Indicated by increase of the third number of the version. (e.g., v2.11.1)
| Release Version | Date | Notes |
|---|---|---|
| v2.27.0 | Jun 11, 2026 | |
| v2.28.0 | Jun 23, 2026 | |
| v2.29.0 | Jul 9, 2026 |
- Release Notes: All updates will be documented in the repository releases.
- Notifications: User's with impacted change requests will be noted for testing in the acceptance environment, as well as when the package is released.
Contributors can view planned features in the issues list and propose changes by creating new issues.