deploy: ruby-prof/ruby-prof@a84326d

Author: cfis

alternatives/index.html

@@ -1035,7 +1035,7 @@ <h2 id="report-formats">Report Formats<a class="headerlink" href="#report-format
 <h2 id="when-to-use-each">When to Use Each<a class="headerlink" href="#when-to-use-each" title="Permanent link">&para;</a></h2>
 <h3 id="ruby-prof">ruby-prof<a class="headerlink" href="#ruby-prof" title="Permanent link">&para;</a></h3>
 <p>ruby-prof is the longest-standing Ruby profiler, with its <a href=".././history/">first</a> release in 2005. It has been continuously maintained for nearly two decades, evolving alongside Ruby itself from 1.8 through 4.0. Over that time it has supported every major Ruby version and platform, including Windows — a rarity among Ruby C extensions.</p>
-<p>Being a tracing profiler, ruby-prof provides <em>exact</em> information about your program. It tracks every thread, every fiber and every method call. It shines with its support for multiple measurements modes and excellent reporting capabilities. </p>
+<p>Being a tracing profiler, ruby-prof provides <em>exact</em> information about your program. It tracks every thread, every fiber and every method call. It shines with its support for multiple measurement modes and excellent reporting capabilities. </p>
 <p>ruby-prof can be used from the <a href="../getting-started/#command-line">command line</a> with no code changes, or via an API for more control.</p>
 <p>The biggest downsides of ruby-prof are:</p>
 <ul>

changelog/index.html

@@ -539,6 +539,17 @@
     </label>
     <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
 
+        <li class="md-nav__item">
+  <a href="#204-2026-03-03" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        2.0.4 (2026-03-03)
+      
+    </span>
+  </a>
+  
+</li>
+      
         <li class="md-nav__item">
   <a href="#203-2026-02-28" class="md-nav__link">
     <span class="md-ellipsis">
@@ -1673,6 +1684,17 @@
     </label>
     <ul class="md-nav__list" data-md-component="toc" data-md-scrollfix>
 
+        <li class="md-nav__item">
+  <a href="#204-2026-03-03" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        2.0.4 (2026-03-03)
+      
+    </span>
+  </a>
+  
+</li>
+      
         <li class="md-nav__item">
   <a href="#203-2026-02-28" class="md-nav__link">
     <span class="md-ellipsis">
@@ -2791,6 +2813,11 @@
 
 
 <h1 id="changelog">Changelog<a class="headerlink" href="#changelog" title="Permanent link">&para;</a></h1>
+<h2 id="204-2026-03-03">2.0.4 (2026-03-03)<a class="headerlink" href="#204-2026-03-03" title="Permanent link">&para;</a></h2>
+<ul>
+<li>Fix NoMethodError when sort_method is nil (issue #349)</li>
+<li>Fix broken source_code_uri on rubygems.org (issue #350)</li>
+</ul>
 <h2 id="203-2026-02-28">2.0.3 (2026-02-28)<a class="headerlink" href="#203-2026-02-28" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Remove unnecessary visited set from FlameGraphPrinter (call tree is always acyclic)</li>
@@ -2820,7 +2847,7 @@ <h3 id="features">Features<a class="headerlink" href="#features" title="Permanen
 <h3 id="backwards-incompatible-changes">Backwards Incompatible Changes<a class="headerlink" href="#backwards-incompatible-changes" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Removed <code>RubyProf::MEMORY</code> measurement mode (no longer works on Ruby 4.0+)</li>
-<li>Rremove compatibility API that was scheduled for removal in 2023</li>
+<li>Remove compatibility API that was scheduled for removal in 2023</li>
 <li>Printer options now use keyword arguments instead of an options hash. For example:
   <div class="language-ruby highlight"><pre><span></span><code><span id="__span-0-1"><a id="__codelineno-0-1" name="__codelineno-0-1" href="#__codelineno-0-1"></a><span class="c1"># Before:</span>
 </span><span id="__span-0-2"><a id="__codelineno-0-2" name="__codelineno-0-2" href="#__codelineno-0-2"></a><span class="n">printer</span><span class="o">.</span><span class="n">print</span><span class="p">(</span><span class="no">STDOUT</span><span class="p">,</span><span class="w"> </span><span class="ss">:min_percent</span><span class="w"> </span><span class="o">=&gt;</span><span class="w"> </span><span class="mi">2</span><span class="p">,</span><span class="w"> </span><span class="ss">:sort_method</span><span class="w"> </span><span class="o">=&gt;</span><span class="w"> </span><span class="ss">:self_time</span><span class="p">)</span>
@@ -2970,7 +2997,7 @@ <h2 id="100-2019-07-29">1.0.0 (2019-07-29)<a class="headerlink" href="#100-2019-
 <ul>
 <li>Profiling is significantly faster - 5x in some cases</li>
 <li>Recursive profiles are finally handled correctly.  Yeah!!!</li>
-<li>Redesigned reports (Chirs Whitefield)</li>
+<li>Redesigned reports (Chris Whitefield)</li>
 <li>New documentation website (<a href="https://ruby-prof.github.io">https://ruby-prof.github.io</a>)</li>
 <li>The ability to measure allocations and memory usage using a standard (unpatched) version of ruby</li>
 <li>The ability to save and reload profiling results for later analysis</li>

history/index.html

@@ -550,7 +550,7 @@
 
 <h1 id="history">History<a class="headerlink" href="#history" title="Permanent link">&para;</a></h1>
 <p>For a full list of changes between versions, see the <a href="../changelog/">Changelog</a>.</p>
-<p>The first version of ruby-prof, 0.1.1, was released on March 22, 2005 by <a href="https://shugo.net/">Shugo Maeda</a> The original <a href="https://shugo.net/archive/ruby-prof/">source</a> code is still available on his website (it is not actually in the git history). ruby-prof was a vast improvement at the time, running 30 times faster as the original ruby profiler.</p>
+<p>The first version of ruby-prof, 0.1.1, was released on March 22, 2005 by <a href="https://shugo.net/">Shugo Maeda</a> The original <a href="https://shugo.net/archive/ruby-prof/">source</a> code is still available on his website (it is not actually in the git history). ruby-prof was a vast improvement at the time, running 30 times faster than the original ruby profiler.</p>
 <p>Version <a href="https://rubygems.org/gems/ruby-prof/versions/0.4.0">0.4.0</a> was the first version packaged as a Ruby gem. Version 0.4.0 also introduced Windows support, thread support and added a number of additional reports such as the graph report in HTML and the call graph report.</p>
 <p>A number of versions were subsequently released, with a 1.0.0 <a href="https://cfis.savagexi.com/2019/07/29/ruby-prof-1-0/">release</a> finally happening in July of 2019. Version 1.0.0 was a major rewrite that significantly improved performance, correctly profiled recursive methods, redesigned reports, added allocation/memory measurement support and introduced saving and reloading profiling results. Since then ruby-prof has continued to evolve along with Ruby with 19 releases.</p>
 <p>Version 2.0.0 will mark the 20<sup>th</sup> release of ruby-prof since the 1.0.0 release. Version 2.0.0 supports Ruby 4 and includes new flame/icicle graph support, revamped reports and improved documentation. The reason for the 2.0.0 jump is because profiling memory sizes has been removed due to changes in Ruby 4.0.0. In addition, the old compatibility API was also removed.</p>

reports/index.html

@@ -1023,7 +1023,7 @@ <h3 id="flame-graph">Flame Graph<a class="headerlink" href="#flame-graph" title=
 </tbody>
 </table>
 <h3 id="call-stack">Call Stack<a class="headerlink" href="#call-stack" title="Permanent link">&para;</a></h3>
-<p>Call stack reports produce a HTML visualization of the time spent in each execution path of the profiled code. Use <code>RubyProf::CallStackPrinter</code> to generate this report. (<a href="../public/examples/reports/call_stack.html" target="_blank">example</a>)</p>
+<p>Call stack reports produce an HTML visualization of the time spent in each execution path of the profiled code. Use <code>RubyProf::CallStackPrinter</code> to generate this report. (<a href="../public/examples/reports/call_stack.html" target="_blank">example</a>)</p>
 <p><img alt="Call Stack Report" src="../../public/images/call_stack.png" /></p>
 <p>Additional options:</p>
 <table>