yard 0.9.28 → 0.9.37

data/templates/default/fulldoc/html/js/full_list.js

@@ -62,8 +62,25 @@ function enableToggles() {
     evt.stopPropagation();
     evt.preventDefault();
     $(this).parent().parent().toggleClass('collapsed');
+    $(this).attr('aria-expanded', function (i, attr) {
+        return attr == 'true' ? 'false' : 'true'
+    });
     highlight();
   });
+
+  // navigation of nested classes using keyboard
+  $('#full_list a.toggle').on('keypress',function(evt) {
+    // enter key is pressed
+    if (evt.which == 13) {
+      evt.stopPropagation();
+      evt.preventDefault();
+      $(this).parent().parent().toggleClass('collapsed');
+      $(this).attr('aria-expanded', function (i, attr) {
+          return attr == 'true' ? 'false' : 'true'
+      });
+      highlight();
+    }
+  });
 }
 
 function populateSearchCache() {
@@ -91,7 +108,7 @@ function enableSearch() {
     }
   });
 
-  $('#full_list').after("<div id='noresults' style='display:none'></div>");
+  $('#full_list').after("<div id='noresults' role='status' style='display: none'></div>");
 }
 
 function ignoredKeyPress(event) {
@@ -154,11 +171,14 @@ function partialSearch(searchString, offset) {
 function searchDone() {
   searchTimeout = null;
   highlight();
-  if ($('#full_list li:visible').size() === 0) {
-    $('#noresults').text('No results were found.').hide().fadeIn();
+  var found = $('#full_list li:visible').size();
+  if (found === 0) {
+    $('#noresults').text('No results were found.');
   } else {
-    $('#noresults').text('').hide();
+    // This is read out to screen readers
+    $('#noresults').text('There are ' + found + ' results.');
   }
+  $('#noresults').show();
   $('#content').removeClass('insearch');
 }
 
@@ -188,6 +208,12 @@ function expandTo(path) {
   $target.addClass('clicked');
   $target.removeClass('collapsed');
   $target.parentsUntil('#full_list', 'li').removeClass('collapsed');
+
+  $target.find('a.toggle').attr('aria-expanded', 'true')
+  $target.parentsUntil('#full_list', 'li').each(function(i, el) {
+    $(el).find('> div > a.toggle').attr('aria-expanded', 'true');
+  });
+
   if($target[0]) {
     window.scrollTo(window.scrollX, $target.offset().top - 250);
     highlight();

data/templates/default/fulldoc/html/setup.rb

@@ -104,6 +104,12 @@ def javascripts_full_list
   %w(js/jquery.js js/full_list.js)
 end
 
+# Sets the HTML language lang="value" where value is the value returned from
+# this method. Defaults to nil which does not set the lang attribute.
+def html_lang
+  nil
+end
+
 def menu_lists
   Object.new.extend(T('layout')).menu_lists
 end
@@ -225,7 +231,8 @@ def class_list(root = Registry.root, tree = TreeContext.new)
     has_children = run_verifier(child.children).any? {|o| o.is_a?(CodeObjects::NamespaceObject) }
     out << "<li id='object_#{child.path}' class='#{tree.classes.join(' ')}'>"
     out << "<div class='item' style='padding-left:#{tree.indent}'>"
-    out << "<a class='toggle'></a> " if has_children
+    accessible_props = "aria-label='#{name} child nodes' aria-expanded='false' aria-controls='object_#{child.path}'"
+    out << "<a tabindex='0' class='toggle' role='button' #{accessible_props}></a> " if has_children
     out << linkify(child, name)
     out << " &lt; #{child.superclass.name}" if child.is_a?(CodeObjects::ClassObject) && child.superclass
     out << "<small class='search_info'>"
@@ -233,7 +240,8 @@ def class_list(root = Registry.root, tree = TreeContext.new)
     out << "</small>"
     out << "</div>"
     tree.nest do
-      out << "<ul>#{class_list(child, tree)}</ul>" if has_children
+      labeled_by = "aria-labelledby='object_#{child.path}'"
+      out << "<div #{labeled_by}><ul>#{class_list(child, tree)}</ul></div>" if has_children
     end
     out << "</li>"
   end

data/templates/default/onefile/html/headers.erb

@@ -1,5 +1,7 @@
 <style type="text/css">
   <%= @css_data %>
+  html { width: auto; height: auto; }
+  body { display: block; margin: 1rem; width: auto; }
 </style>
 <script type="text/javascript">
   <%= @js_data %>

data/templates/default/tags/html/example.erb

@@ -1,9 +1,9 @@
 <% if object.has_tag?(:example) %>
   <div class="examples">
-    <p class="tag_title">Examples:</p>
+    <h4 class="tag_title">Examples:</h4>
     <% object.tags(:example).each do |tag| %>
       <% unless tag.name.empty? %>
-        <p class="example_title"><%= htmlify_line(tag.name) %></p>
+        <h5 class="example_title"><%= htmlify_line(tag.name) %></h5>
       <% end %>
       <pre class="example code"><code><%= html_syntax_highlight(tag.text) %></code></pre>
     <% end %>

data/templates/default/tags/html/option.erb

@@ -1,4 +1,4 @@
-<% if object.has_tag?(:option) %>
+<% if object.has_tag?(:option) && object.respond_to?(:parameters) %>
   <% object.parameters.each do |param, default| %>
     <% tags = object.tags(:option).select {|x| x.name.to_s == param.to_s.sub(/^\*+|:$/, '') } %>
     <% next if tags.empty? %>

metadata

@@ -1,29 +1,15 @@
 --- !ruby/object:Gem::Specification
 name: yard
 version: !ruby/object:Gem::Version
-  version: 0.9.28
+  version: 0.9.37
 platform: ruby
 authors:
 - Loren Segal
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2022-06-01 00:00:00.000000000 Z
-dependencies:
-- !ruby/object:Gem::Dependency
-  name: webrick
-  requirement: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: 1.7.0
-  type: :runtime
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    requirements:
-    - - "~>"
-      - !ruby/object:Gem::Version
-        version: 1.7.0
+date: 2024-09-04 00:00:00.000000000 Z
+dependencies: []
 description: |2
       YARD is a documentation generation tool for the Ruby programming language.
       It enables the user to generate consistent, usable documentation that can be
@@ -37,46 +23,13 @@ executables:
 extensions: []
 extra_rdoc_files: []
 files:
-- ".dockerignore"
-- ".gitattributes"
-- ".github/FUNDING.yml"
-- ".github/ISSUE_TEMPLATE.md"
-- ".github/PULL_REQUEST_TEMPLATE.md"
-- ".github/workflows/ci.yml"
-- ".github/workflows/gem.yml"
-- ".gitignore"
-- ".rspec"
-- ".rubocop.yml"
 - ".yardopts"
 - ".yardopts_guide"
 - ".yardopts_i18n"
 - CHANGELOG.md
-- CODE_OF_CONDUCT.md
-- CONTRIBUTING.md
-- Dockerfile.samus
-- Gemfile
 - LEGAL
 - LICENSE
 - README.md
-- Rakefile
-- SECURITY.md
-- benchmarks/builtins_vs_eval.rb
-- benchmarks/concat_vs_join.rb
-- benchmarks/erb_vs_erubis.rb
-- benchmarks/format_args.rb
-- benchmarks/generation.rb
-- benchmarks/marshal_vs_dbm.rb
-- benchmarks/parsing.rb
-- benchmarks/pathname_vs_string.rb
-- benchmarks/rdoc_vs_yardoc.rb
-- benchmarks/registry_store_types.rb
-- benchmarks/ri_vs_yri.rb
-- benchmarks/ripper_parser.rb
-- benchmarks/splat_vs_flatten.rb
-- benchmarks/template_erb.rb
-- benchmarks/template_format.rb
-- benchmarks/template_profile.rb
-- benchmarks/yri_cache.rb
 - bin/yard
 - bin/yardoc
 - bin/yri
@@ -212,6 +165,7 @@ files:
 - lib/yard/i18n/pot_generator.rb
 - lib/yard/i18n/text.rb
 - lib/yard/logging.rb
+- lib/yard/open_struct.rb
 - lib/yard/options.rb
 - lib/yard/parser/base.rb
 - lib/yard/parser/c/c_parser.rb
@@ -259,6 +213,7 @@ files:
 - lib/yard/server/commands/static_file_helpers.rb
 - lib/yard/server/doc_server_helper.rb
 - lib/yard/server/doc_server_serializer.rb
+- lib/yard/server/http_utils.rb
 - lib/yard/server/library_version.rb
 - lib/yard/server/rack_adapter.rb
 - lib/yard/server/router.rb
@@ -311,9 +266,6 @@ files:
 - lib/yard/verifier.rb
 - lib/yard/version.rb
 - po/ja.po
-- samus.json
-- tasks/prepare_tag.rake
-- tasks/update_error_map.rake
 - templates/default/class/dot/setup.rb
 - templates/default/class/dot/superklass.erb
 - templates/default/class/html/constructor_details.erb
@@ -441,7 +393,6 @@ files:
 - templates/guide/onefile/html/setup.rb
 - templates/guide/onefile/html/toc.erb
 - templates/guide/tags/html/setup.rb
-- yard.gemspec
 homepage: http://yardoc.org
 licenses:
 - MIT
@@ -462,7 +413,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.2
+rubygems_version: 3.3.5
 signing_key: 
 specification_version: 4
 summary: Documentation tool for consistent and usable documentation in Ruby.

data/.dockerignore

@@ -1,2 +0,0 @@
-doc
-.yardoc

data/.gitattributes

@@ -1,4 +0,0 @@
-# Auto detect text files and perform LF normalization
-* text eol=lf
-
-*.png binary

data/.github/FUNDING.yml

@@ -1,3 +0,0 @@
-# These are supported funding model platforms
-
-github: lsegal

data/.github/ISSUE_TEMPLATE.md

@@ -1,33 +0,0 @@
-[Describe your issue here. Try to be as specific as possible so we can find
-the root cause more quickly!]
-
-## Steps to reproduce
-
-This is the minimal reproduction for the issue. I've done my best to remove
-all extraneous code and unique environment state on my machine before providing
-these steps:
-
-1. Run the following command: `yard doc --no-private`
-2. Open browser to (URL)...
-3. Click on Method List link.
-
-## Actual Output
-
-[Provide the full output (**please run yard with `--debug`**) or screenshots for
-visual issues.]
-
-## Expected Output
-
-[Describe what you *expected* to happen.]
-
-## Environment details:
-
-- OS: [Enter operating system / version here]
-- Ruby version (`ruby -v`): [Enter output of `ruby -v`]
-- YARD version (`yard -v`): [Enter output of `yard -v`]
-- Relevant software dependency/versions:
-  - [Any 3rd party libs required to reproduce, omit if none]
-
-I have read the [Contributing Guide][contrib].
-
-[contrib]: https://github.com/lsegal/yard/blob/main/CONTRIBUTING.md

data/.github/PULL_REQUEST_TEMPLATE.md

@@ -1,12 +0,0 @@
-# Description
-
-Describe your pull request and problem statement here.
-
-# Completed Tasks
-
-- [ ] I have read the [Contributing Guide][contrib].
-- [ ] The pull request is complete (implemented / written).
-- [ ] Git commits have been cleaned up (squash WIP / revert commits).
-- [ ] I wrote tests and ran `bundle exec rake` locally (if code is attached to PR).
-
-[contrib]: https://github.com/lsegal/yard/blob/main/CONTRIBUTING.md

data/.github/workflows/ci.yml

@@ -1,30 +0,0 @@
-name: Unit Tests
-
-on: [push, pull_request, workflow_dispatch]
-jobs:
-  build:
-    name: "Ruby: ${{ matrix.ruby }} OS: ${{ matrix.os }}"
-    runs-on: ${{ matrix.os }}
-    strategy:
-      fail-fast: false
-      matrix:
-        os: [ubuntu-20.04, macos-10.15, windows-2019]
-        # 3.0 is interpreted as 3. also disable 2.5 due to bundler crashes
-        ruby: [2.2, 2.3, 2.4, 2.6, 2.7, "3.0", 3.1]
-        exclude:
-          - { os: windows-2019, ruby: 2.2 }
-          - { os: windows-2019, ruby: 2.3 }
-    steps:
-      - name: Checkout
-        uses: actions/checkout@v2
-      - name: Install Ruby & 'bundle install'
-        uses: ruby/setup-ruby@v1
-        with:
-          ruby-version: ${{ matrix.ruby }}
-          bundler-cache: true
-      - name: Run Test
-        run: |
-          ruby -v
-          bundle exec rake
-        env:
-          CI: true

data/.github/workflows/gem.yml

@@ -1,19 +0,0 @@
-name: Release Version
-
-on:
-  push:
-    tags:
-      - "v*"
-
-jobs:
-  release_version:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v2
-      - uses: lsegal/github-release-from-changelog-action@latest
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-      - name: Publish RubyGem
-        uses: dawidd6/action-publish-gem@v1
-        with:
-          api_key: ${{secrets.RUBYGEMS_API_KEY}}

data/.gitignore

@@ -1,14 +0,0 @@
-_Yardoc
-.DS_Store
-*.rbc
-*.pdf
-.yardoc
-*.gem
-Gemfile.lock
-/pkg
-/doc
-/doc_guide
-/coverage
-/.bundle
-/vendor
-spec/examples.txt

data/.rspec

@@ -1,2 +0,0 @@
---color
---require spec_helper

data/.rubocop.yml

@@ -1,112 +0,0 @@
-#inherit_from:
-#  - .rubocop_todo.yml
-
-Metrics:
-  Enabled: false
-Layout/LineLength:
-  AutoCorrect: true
-  Max: 100
-Style/Semicolon:
-  AllowAsExpressionSeparator: true
-Style/Documentation:
-  Enabled: false
-Style/ClassVars:
-  Enabled: false
-Style/HashSyntax:
-  EnforcedStyle: hash_rockets
-Layout/SpaceInsideHashLiteralBraces:
-  EnforcedStyle: no_space
-Layout/SpaceInsideBlockBraces:
-  SpaceBeforeBlockParameters: false
-Style/NumericPredicate: # ruby 1.8/1.9 do not have positive?/negative?
-  EnforcedStyle: comparison
-Layout/MultilineMethodCallIndentation:
-  EnforcedStyle: indented
-Layout/DotPosition:
-  EnforcedStyle: trailing
-Style/FormatString:
-  EnforcedStyle: percent
-Layout/FirstArrayElementIndentation:
-  EnforcedStyle: consistent
-Layout/FirstHashElementIndentation:
-  EnforcedStyle: consistent
-
-# Disable these until we know what to do with them
-Style/SafeNavigation:
-  Enabled: false # not supported in 1.8...2.1
-Style/GuardClause: # does not provide much value
-  Enabled: false
-Naming/VariableNumber:
-  Enabled: false
-Naming/AccessorMethodName: # this creates breaking changes in the API
-  Enabled: false
-Naming/PredicateName: # this creates breaking changes in the API
-  Enabled: false
-Style/MethodMissingSuper: # this doesn't exist in 1.8/1.9
-  Enabled: false
-Style/MissingRespondToMissing: # this doesn't exist in 1.8/1.9
-  Enabled: false
-Style/Lambda: # not supported in 1.8
-  Enabled: false
-Style/EachWithObject: # not supported in 1.8
-  Enabled: false
-Layout/ParameterAlignment: # does not work correctly with subsequent block
-  Enabled: false
-Layout/ArrayAlignment: # does not support indentation
-  Enabled: false
-Layout/HashAlignment: # does not support indentation
-  Enabled: false
-Style/MultilineTernaryOperator:
-  Enabled: false
-Style/ClassAndModuleChildren:
-  Enabled: false
-Layout/EmptyLineBetweenDefs:
-  AllowAdjacentOneLineDefs: true
-Style/SingleLineMethods:
-  Enabled: false
-Style/SingleLineBlockParams:
-  Enabled: false
-Style/NestedTernaryOperator:
-  Enabled: false
-Style/MutableConstant:
-  Enabled: false
-Style/WhenThen:
-  Enabled: false
-Style/StringLiterals:
-  Enabled: false
-Style/StringLiteralsInInterpolation:
-  Enabled: false
-Style/PerlBackrefs:
-  Enabled: false
-Style/BlockComments:
-  Exclude:
-    - benchmarks/*.rb
-Style/CaseEquality:
-  Enabled: false
-Style/WordArray:
-  Enabled: false
-Style/GlobalVars:
-  Exclude:
-    - benchmarks/**/*.rb
-    - spec/**/*.rb
-Lint/RedundantSplatExpansion:
-  Enabled: false
-Security/Eval:
-  Exclude:
-    - benchmarks/**/*.rb
-    - spec/**/*.rb
-
-Layout/SpaceAroundMethodCallOperator:
-  Enabled: false
-Lint/RaiseException:
-  Enabled: false
-Lint/StructNewOverride:
-  Enabled: false
-Style/ExponentialNotation:
-  Enabled: false
-Style/HashEachMethods:
-  Enabled: false
-Style/HashTransformKeys:
-  Enabled: false
-Style/HashTransformValues:
-  Enabled: false

data/CODE_OF_CONDUCT.md

@@ -1,15 +0,0 @@
-This document provides community guidelines for a safe, respectful, productive,
-and collaborative place for any person who is willing to contribute to the YARD
-project. It applies to all “collaborative space”, which is defined as community
-communications channels (such as mailing lists, submitted patches, commit
-comments, etc.).
-
-* Participants will be tolerant of opposing views.
-
-* Participants must ensure that their language and actions are free of personal
-  attacks and disparaging personal remarks.
-
-* When interpreting the words and actions of others, participants should always
-  assume good intentions.
-
-* Behaviour which can be reasonably considered harassment will not be tolerated.

data/CONTRIBUTING.md

@@ -1,140 +0,0 @@
-# Contributing Guide
-
-## Help YARD Help You!
-
-**YARD thrives off of the contributions of its users**. This project will gladly
-review pull requests and issues. This document outlines how to maximize
-the chance of a reported issue being resolved or pull request being accepted.
-
-## Code of Conduct
-
-**All reported issues, pull requests, communication, and code related to YARD**
-**must follow the [Code of Conduct][code] or they will be moderated immediately**.
-Please take time to familiarize yourself with the Code of Conduct before
-you get started. Fundamentally, **you are expected to behave with respect** to all
-other users.
-
-## Filing a Bug Report
-
-**You can submit bug reports on our [GitHub issue tracker][issues]**.
-
-If you believe you have found a bug, please include a few things in your report:
-
-1. **A minimal reproduction of the issue**. Providing a huge blob of code is
-   better than nothing, but providing the shortest possible set of instructions
-   is even better. Take out any instructions or code that, when removed, have
-   no effect on the problematic behavior. The easier your bug is to triage and
-   diagnose, the higher up in the priority list it will go. We can do this stuff,
-   but limited time means this may not happen immediately. Make your bug report
-   extremely accessible and you will almost guarantee a quick fix.
-
-2. **Your environment and relevant versions**. Please include your Ruby,
-   YARD, and system versions (including OS) when reporting a bug. This
-   makes it easier to diagnose problems. If the issue or stack trace
-   includes another library, consider also listing any dependencies
-   that may be affecting the issue. This is where a minimal reproduction
-   case helps a lot.
-
-3. **Your expected result**. Tell us what you think should happen. This
-   helps us to understand the context of your problem. Many complex features
-   can contain ambiguous usage, and your use case may differ from the
-   intended one. If we know your expectations, we can more easily determine
-   if the behavior is intentional or not.
-
-Finally, please **DO NOT** submit a report that states a feature simply
-_"does not work"_ without any additional information in the report. Consider
-the issue from the maintainer's perspective: in order to fix your bug, we
-need to drill down to the broken line of code, and in order to do this,
-we must be able to reproduce the issue on our end to find that line of
-code. The easier we can do this, the quicker your bug gets fixed. Help
-us help you by providing as much information as you possibly can. We may
-not have the tools or environment to properly diagnose your issue, so
-your help may be required to debug the issue.
-
-Also **consider opening a pull request** to fix the issue yourself if you can.
-This will likely speed up the fix time significantly. See below for
-information on how to do this.
-
-## Asking a Question
-
-**Questions are accepted on [GitHub issues][issues], but consider signing up**
-**for the [YARD mailing list][ml]** and asking it there so that we can organize
-issues appropriately. You can also hop onto IRC (irc.freenode.net / #yard)
-for quick questions.
-
-## Asking for a Feature
-
-**YARD does not currently accept feature requests filed as GitHub issues**. If
-you are looking to have a feature implemented into YARD, consider doing this
-yourself and [submitting a pull request][pr] (PR) with your work. If the work
-required is involved, consider starting a discussion on the [mailing list][ml]
-or opening an issue to ask a question; we will be happy to have a conversation
-and let you know if the feature would be considered. They usually are, but
-it might be prudent to ask first!
-
-Please do not fret if your feature request gets closed immediately. We do this
-to keep our issue tracker clean. **Closing an issue does not mean it would not**
-**be accepted as a pull request**. If the feature would not be accepted as a
-PR, this will be communicated in the closed issue.
-
-## Making a Change via Pull Request
-
-**You can also submit pull requests on our [GitHub issue tracker][issues]**.
-
-If you've been working on a patch or feature that you want in YARD, here are
-some tips to ensure the quickest turnaround time on getting it merged in:
-
-1. **Keep your changes small**. If your feature is large, consider splitting
-   it up into smaller portions and submit pull requests for each component
-   individually. Feel free to describe this in your first PR or on the
-   mailing list, but note that it will be much easier to review changes
-   if they affect smaller portions of code at a time.
-
-2. **Keep commits brief and clean**: YARD uses Git and tries to maintain a
-   clean repository. Please ensure that you use [commit conventions][commit]
-   to make things nice and neat both in the description and commit history.
-   Specifically, consider squashing commits if you have partial or complete
-   reverts of code. Each commit should provide an atomic change that moves
-   the project forwards, not back. Any changes that only fix other parts of
-   your PR should be hidden from the commit history.
-
-3. **Follow our coding conventions**. YARD uses typical Ruby source formatting,
-   though it occasionally has minor differences with other projects you may
-   have seen. Please look through a few files (at least the file you are
-   editing) to ensure that you are consistent in the formatting your PR is
-   using.
-
-4. **Make sure you have tests**. Not all changes require tests, but if your
-   changes involve code, you should consider adding at least one new test
-   case for your change (and ideally a couple of tests). This will add
-   confidence when reviewing and will make accepting the change much easier.
-
-5. **Make sure ALL the tests pass**. YARD has a fairly large suite of tests.
-   Please make sure you can run all of the tests (`bundle exec rake`) prior
-   to submitting your PR. Please also remember that YARD supports a number
-   of environments, including OS X, Linux, Windows, and a number of older
-   Ruby versions (1.8+), so if you can test under these environments, that
-   helps (but is not required). At the very least, be aware of this fact
-   when submitting code.
-
-If your change is large, consider starting a discussion on the [mailing list][ml]
-or opening an issue to ask a question; we will be happy to have a conversation
-and let you know if the feature would be considered. They usually are, but
-it might be prudent to ask first!
-
-## Maintainers
-
-**Interested in helping to maintain YARD? Email [lsegal@soen.ca][mail]** for more
-information. Offering to be a project maintainer is an important contribution
-to open source software, and your work will be highly valued in the community.
-If you have been a contributor, consider being a member of the core team to
-help handle day-to-day operations, such as releases, bug fixes, and triage.
-You can do some of this as a non-maintainer too, but if you like this project,
-we can always use more hands on deck!
-
-[code]: https://github.com/lsegal/yard/blob/main/CODE_OF_CONDUCT.md
-[issues]: http://github.com/lsegal/yard/issues
-[commit]: http://chris.beams.io/posts/git-commit/
-[pr]: https://help.github.com/articles/using-pull-requests/
-[ml]: https://groups.google.com/forum/#!forum/yardoc
-[mail]: mailto:lsegal@soen.ca

data/Dockerfile.samus

@@ -1,28 +0,0 @@
-FROM lsegal/samus:latest as samus
-
-FROM ruby:2
-ARG VERSION
-ENV VERSION=${VERSION}
-WORKDIR /github/lsegal/yard
-ENTRYPOINT samus publish release-v${VERSION}.tar.gz
-
-# Prepare credential config
-RUN mkdir -p ~/.ssh
-RUN echo "Host *" > ~/.ssh/config
-RUN echo "    StrictHostKeyChecking no" >> ~/.ssh/config
-RUN chmod 400 ~/.ssh/config
-COPY ./.samusprep/.samus /root/.samus
-COPY ./.samusprep/.gitconfig /root/.gitconfig
-
-# Setup Samus
-ENV PATH=$PATH:/samus/bin
-COPY --from=samus /samus /samus
-
-# Install gems
-ENV BUNDLE_PATH=/var/gems
-COPY Gemfile /github/lsegal/yard
-RUN bundle
-
-# Run build
-COPY . /github/lsegal/yard
-RUN samus build --skip-restore ${VERSION}