Skip to content

Skip CI & memcheck when pushing v* tags#120

Merged
jbourassa merged 1 commit intomainfrom
ignore-ci-for-tags
Jan 23, 2023
Merged

Skip CI & memcheck when pushing v* tags#120
jbourassa merged 1 commit intomainfrom
ignore-ci-for-tags

Conversation

@jbourassa
Copy link
Copy Markdown
Collaborator

This should not be needed assuming main is green. It'll speed up builds and avoid wasting resources.

@jbourassa jbourassa merged commit f1e120f into main Jan 23, 2023
@jbourassa jbourassa deleted the ignore-ci-for-tags branch February 16, 2023 13:12
jbourassa added a commit that referenced this pull request Sep 19, 2024
YARD doc generation is broken in a few different ways, this change aims
to fix all the known issues. Fixes #342.

**Issues:**

1. Docs for tagged releases (vx.y.z tags) was last generated for
   v6.0.0 because we stopped running CI in on versions in #120. This
   means that the current "latest" doc symlink points to v6.0.0, helping
   other doc issues go unnoticed (see next points).

   Fix: run the doc generation step on release as well.

2. YARD doc generation stopped working at some point last year when we
   updated the nightly version. The doc for main only has a handful of
   Ruby-defined APIs, but none of the Rust-defined APIs. The root cause
   is a change in rustdoc's JSON format which caused yard-rustdoc
   to miss all definitions.

   Fix: teach yard-rustdoc about the new format, and update the
   dependency. This will also fix an issue causing
   `Wasmtime::Memory::UnsafeSlice` to not show up in the class list
   sidebar.
   See: oxidize-rb/yard-rustdoc@v0.3.2...v0.4.0

3. Documentation entries had issues (invalid names, missing args, etc.)
   This would normally be caught in CI, but they weren't given the docs
   for Rust-defined APIs were skipped (see above point).
@jbourassa jbourassa mentioned this pull request Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants