One link for every revision of a board
Why a board's link should outlive its revisions, and how BoardRepo keeps one address on the latest version while every older version stays numbered, linkable and downloadable.
Published
Hardware links go stale quickly. A shared-drive folder gets reorganised, a zip attached to an email is superseded by the next email, and a link to a file in a repository points at whatever that file became. The README, the issue tracker and the fab's order history end up pointing at three different revisions, or at nothing.
A board page on BoardRepo is built so that one address stays right.
The link follows the latest version
A board lives at one address, boardrepo.com/<owner>/<board>. Each upload or GitHub sync adds a numbered version behind it, and that address always opens the newest one. Put it in your README, your issue tracker and your notes to the assembler once. Nobody has to edit those when revision C replaces revision B.
Older versions keep their own links
Open Version history on the board to see every published version with its note. Opening an older one adds its number to the address, as ?v=3, so you can send someone revision 3 specifically, and that link still shows revision 3 after revision 4 exists. Each version keeps the exact files it was published with, downloadable as a zip, and its own rendered schematic and PCB.
Tracking a GitHub repository
If the design already lives on GitHub, import the repository instead of uploading zips. With the BoardRepo GitHub App installed and Keep up to date selected, pushes to the default branch become new versions, so the BoardRepo link follows the repository without anyone uploading again.
What belongs in a version
A version is only useful if it opens. Upload the whole project folder: the schematic and layout, the libraries they reference, the 3D models, and the fabrication outputs you actually ordered. Add a short note saying what changed and why. Version control for PCB designs covers the routine in more detail, and version control for KiCad projects covers what to commit if the board is also in git.
Going back
Restoring an older version as the latest is one action in Version history. It creates a new version rather than rewriting the old ones, so the board's address moves back to the good revision and the history still shows what happened. Two published versions can also be compared on the board, with the changed parts, routing and outline highlighted.
More in News.